Login Form

ISC2 East Bay Chapter

Some Reading Ideas

Risk Management Framework - RMF SP 800-37

Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy (nist.gov)

Prepare Essential activities to prepare the organization to manage security and privacy risks.

Implement the controls and document how controls are deployed.

Categorize the system and information processed, stored, and transmitted based on impact analysis. 

Assess to determine if the controls are in place, operating as intended, and producing the desired results. 

Select the set of NIST SP 800-53 controls to protect the system based on risk assessment(s)

Authorize: Senior official makes a risk-based decision to authorize the system (to operate).

Monitor: Continuously monitor control implementation and risks to the system. 
Table 1: RMF Steps Including Resources for Implementers and Supporting NIST Publications *Read More at Risk Management Framework (RMF) Overview - Risk Management | CSRC

Cybersecurity Framework

Cybersecurity Framework (CSF) Framework Core (nist.gov)

Identify –   Develop an organizational understanding to manage cybersecurity risk to systems, people, assets, data, and capabilities. The activities in the Identify Function are foundational for effective use of the Framework. Understanding the business context, the resources that support critical functions, and the related cybersecurity risks enables an organization to focus and prioritize its efforts, consistent with its risk management strategy and business needs. Examples of outcome Categories within this Function include Asset Management; Business Environment; Governance; Risk Assessment; and Risk Management Strategy.

Protect – Develop and implement appropriate safeguards to ensure delivery of critical services. The Protect Function supports the ability to limit or contain the impact of a potential cybersecurity event. Examples of outcome Categories within this Function include Identity Management and Access Control; Awareness and Training; Data Security; Information Protection Processes and Procedures; Maintenance; and Protective Technology.

Detect – Develop and implement appropriate activities to identify the occurrence of a cybersecurity event. The Detect Function enables the timely discovery of cybersecurity events. Examples of outcome Categories within this Function include Anomalies and Events; Security Continuous Monitoring; and Detection Processes. 

Respond – Develop and implement appropriate activities to take action regarding a detected cybersecurity incident. The Respond Function supports the ability to contain the impact of a potential cybersecurity incident. Examples of outcome Categories within this Function include Response Planning; Communications; Analysis; Mitigation; and Improvements.

Recover – Develop and implement appropriate activities to maintain plans for resilience and to restore any capabilities or services that were impaired due to a cybersecurity incident. The Recover Function supports timely recovery to normal operations to reduce the impact of a cybersecurity incident. Examples of outcome Categories within this Function include Recovery Planning; Improvements; and Communications. 

Read more about NIST Cybersecurity Framework CSF

Process Transformation

The Agile Organization - Absolutely. So how do we do it?

Details
Written by: Paul Bayne - In memory of
Parent Category: Services
Category: Process Transformation

Article Index

Page 2 of 2

Absolutely. So how do we do it?

Compliance has typically been a relatively static area since it rarely goes away once a regulation is implemented. This leads to inefficiencies as new processes and systems are dropped on top of old methods without reviewing the entire Compliance structure, operations, tools, and objectives.

First, let’s review some of the critical tenets of Agile.

  1. The customer value measures all the work it adds. Compliance has two customers: the company’s end customer and the regulatory agency that oversees the company. These two may have conflicting desires and objectives, so it’s essential to understand exactly what each team wants.
  2. Projects should be broken down into the lowest viable release. A release can be software or a business process, new or changed.
  3. Developing the backlog of what needs to be done and prioritizing the backlog. This is a joint effort between all stakeholders-business, technology, and compliance.

The first step is to identify what needs to be done. It’s easy to locate the new regulation that we need to comply with, but if the thought of adding one more series of reports to the monthly stack fills you with dread, then examine your Compliance eco-system as a whole. Keep in mind who your customer is!

  • Where does your data originate?
  • Is the data manipulated in spreadsheets, opening you to errors? Or does the data you receive need to be cleaned or adjusted before submitting it?
  • How labor intensive is it to get the data you need?
  • Are your technology tools working for the benefit of your customers?
  • Do we provide a summary and detailed data in a format that our customers can easily consume? When did you last ask them what they wanted?
  • Are the Compliance requirements built into the product development process?
  • Are Internal Controls embedded in our tools and processes or tacked on afterward?

The answers to these questions will lead you to develop your backlog of work. In most cases, your backlog items will need to be split into more granular problems and solutions at the first pass. Keep breaking until each idea is decomposed into the minimum viable product, the smallest unit that can be delivered and still add value to your customers. Now, prioritize the backlog, and start your first sprint with the highest priority item.

Keep in mind that Agile fosters continuous improvement. Don’t let your backlog stay static. Keep adding items to your backlog that benefit your customers, and remember that Agile is a journey, not a destination!

If you’d like help implementing Agile in your business processes, reach out. We know so many experts in this space, and we can certainly guide your following conversation.

This article was originally authored by Paul Bayne.

Paul left this world after a courageous and inspiring fight with brain cancer. https://www.gofundme.com/f/a-film-on-life-after-a-terminal-cancer-diagnosis 

Hits: 1051
Main Menu

FIPS PUB 200 Minimum Security Requirements

FIPS PUB 200 Minimum Security Requirements - Visit FIPS 200, Minimum Security Requirements for Federal Info and Info Systems | CSRC (nist.gov)
  • Access Control (AC)
  • Awareness and Training (AT)
  • Audit and Accountability (AU)
  • Certification, Accreditation, and Security Assessments (CA)
  • Configuration Management (CM)
  • Contingency Planning (CP)
  • Identification and Authentication (IA)
  • Incident Response (IR)

Read FIPS PUB 200 Minimum Security Requirements
  • Maintenance (MA)
  • Media Protection (MP)
  • Physical and Environmental Protection (PE)
  • Planning (PL)
  • Personnel Security (PS)
  • Risk Assessment (RA)
  • System and Services Acquisition (SA)
  • System and Communications Protection (SC)
  • System and Information Integrity (SI)

Standards.gov | NIST

Standards.gov | NIST
Documentary Standards can specify the definition of terms; classifications of components; delineation of procedures; specification of dimensions, materials, processes, products, systems, services, or practices; test methods and sampling procedures; or descriptions of fit and measurements of size or strength. Under the National Technology Transfer and Advancement Act (NTTAA), NIST is assigned the responsibility to coordinate federal, state, and local documentary standards and conformity assessment activities.
Standards.gov | Federal Use of Standards | Standards Incorporated by Reference (SIBR) | Industry Standards | International Standards | Military Standards | Standards Issued or Adopted by Federal Agencies | Standards Search Engines | Voluntary Product Standards

NIST Reading

Whether you're preparing for Cybersecurity certification, working with government standards, or simply starting your career in compliance, these are the NIST Federal Information Processing Standards (FIPS), Special Publication (SP), and Interagency Report (IR) topics you need to know. (The Perils of Mount Must Read™ Confessions of a Cliff Note Junky) These resources go onto the "Mountain of Must Read". If you don't recognize the standard reference, you've missed critical understanding. As of 2022, this is the minimum NIST alphabet. All of these documents are found at https://csrc.nist.gov/publications/ Be very careful about static content. Look at links before you launch them. Never use alternate sites for the Computer Security Resource Center. Get the full list here <NIST Reading Extended>

FIPS Publication 140-2 Security Requirements for Cryptographic Modules [FIPS 140-2]
FIPS Publication 199 Standards for Security Categorization of Federal Information and Information Systems [FIPS 199]
FIPS Publication 200 Minimum Security Requirements for Federal Information and Information Systems [FIPS 200]
FIPS Publication 201-1 Personal Identity Verification (PIV) of Federal Employees and Contractors [FIPS 201-1]		 NISTIR 8212 ISCMA: An Information Security Continuous Monitoring Program Assessment
NIST SP 800-18 Guide for Developing Security Plans for Federal Information Systems [SP 800-18]
NIST SP 800-30 Risk Management Guide for Information Technology Systems [NIST SP 800-30]
NIST SP 800-34 Contingency Planning Guide for Federal Information Systems [SP 800-34]

US Cert CISA Tweets