Author: Ryan Brady

Ryan Brady is a Cybersecurity Analyst for ProObject. He is responsible for researching, reviewing, and maintaining internal security documents required by compliance frameworks such as NIST SP 800-171. Additionally, Ryan interfaces with the system administration team to help harden and maintain availability of ProObject’s network based on best practices and compliance requirements. His background is rather unique and diverse. Ryan was awarded a B.S. in Political Science and Government from Towson University in 2015 with a focus on geopolitics. From there Ryan was awarded an M.S. of Cybersecurity and an MBA from University of Maryland, University College (UMUC) in 2017 and 2018 respectively. Professionally, Ryan has had experiences working for the Maryland State Legislature in various capacities, a biomedical company, an IT company, and now has been working for ProObject since January 2018 developing their cybersecurity compliance practice known as CYBRX.

From the Winter 2019 Issue

Designing Compliance: To Cloud or Not to Cloud?

Author(s):

Ryan Brady, Cybersecurity Analyst, ProObject

RyanBrady-feature-image-wn19

Organizations implementing a new corporate network may find it more practical to not deploy and manage an on-premises network infrastructure (e.g., a network with local internally managed servers). The cloud provides an attractive alternative. Data storage, virtualization, software development, and system management are all managed offsite by cloud service providers. These offerings collectively comprise software … Read more

From the Fall 2018 Issue

Compliance: Complexity to Simplicity

Author(s):

Ryan Brady, Cybersecurity Analyst, ProObject

compliance header

Simplifying NIST SP 800-171 Compliance Process Since the contracting community has grown substantially, it also has led to a series of high profile breaches. These breaches involved the exfiltration of government data from contractors who were victims of hacks or insider threats. Incident response and forensics usually find the contractor was not updating systems regularly … Read more