SMSMC Blog

Understanding the Importance of OMB Directives M-21-31 and M-22-09 to U.S. Federal Agencies

What OMB memoranda M-21-31 (event logging) and M-22-09 (Zero Trust strategy) require of federal agencies, and how the two work together.

By Jim Venuto

When investigators traced the SolarWinds intrusion in late 2020, the questions that mattered most, such as which accounts the attackers used and when, could only be answered where the right logs had been collected and kept long enough. Two Office of Management and Budget (OMB) memoranda issued since then are designed to make that the norm across the federal government.

Introduction

In an era where cyber threats are becoming increasingly sophisticated, federal agencies are under immense pressure to safeguard national security assets and sensitive data. Following Executive Order 14028 on Improving the Nation’s Cybersecurity (May 2021), OMB issued M-21-31 on August 27, 2021, and M-22-09 on January 26, 2022. These directives mandate crucial security improvements, such as enhanced event logging and the adoption of zero-trust architecture, to mitigate the risks associated with cyber threats.

As stewards of national security, federal agencies are subject to stringent regulations that demand advanced cybersecurity measures. This article outlines these new OMB directives’ key facets and advantages, focusing on comprehensive event logging and zero-trust principles.

Essential Requirements and Guidelines of OMB M-21-31 and M-22-09

Understanding the essential requirements and guidelines of OMB M-21-31 and M-22-09 is crucial for federal agencies aiming to bolster their cybersecurity measures. These directives are not mere suggestions; they are stringent rules designed to enhance the security posture of government systems and improve their resilience against cyber threats.

M-21-31 defines four event logging maturity tiers, from EL0 (not effective) to EL3 (advanced), and gives agencies deadlines to reach each one: EL1 within one year, EL2 within 18 months and EL3 within two years. It specifies which logs to keep and for how long, generally 12 months in active storage and a further 18 months in cold storage, and requires agencies to centralize log access and share logs with CISA and the FBI when needed for an investigation. The benefit of this centralized approach is that it enables comprehensive monitoring and analysis, making it easier to spot anomalies or security incidents. For instance, if an unauthorized user attempts to access a system, centralized logging would flag this activity across all systems, allowing for a quicker and more coordinated response.

The directive doesn’t stop at logging; it also emphasizes the need for real-time alerting and reporting mechanisms. This ensures that agencies can respond to security incidents promptly, minimizing potential damage. Imagine a scenario where a malware attack is detected; real-time alerts would enable immediate action, potentially averting a significant data breach.

Moving beyond event logging, OMB M-22-09 sets a federal Zero Trust strategy, organized around the five pillars of CISA’s Zero Trust Maturity Model: identity, devices, networks, applications and workloads, and data. It requires agencies to meet specific goals by the end of fiscal year 2024, including phishing-resistant multi-factor authentication for staff, contractors and partners, a complete inventory of devices, encryption of DNS requests and HTTP traffic, and treating internal applications as if they were exposed to the internet. Zero Trust assumes that no user or device is trusted by default, whether inside or outside the network, and in a world where insider threats are as real as external attackers, that assumption is sound.

These OMB directives lay down a robust framework federal agencies must follow to enhance their cybersecurity measures. From centralized event logging to adopting a zero-trust architecture, these guidelines are designed to provide a multi-layered defense against the ever-evolving landscape of cyber threats.

How Event Logging Enhances Cybersecurity

Effective event logging offers several benefits in enhancing cybersecurity.

Firstly, it gives organizations real-time visibility into their systems, allowing them to detect and respond to security incidents promptly. By monitoring event logs, organizations can identify suspicious activities, such as unauthorized access attempts, malware infections, or data breaches, and take appropriate action to mitigate the risks.

Secondly, event logging enables organizations to conduct comprehensive forensic investigations during security breaches. Detailed event logs help reconstruct the events leading up to the incident, identify the root cause, and determine the damage’s extent. This information is invaluable for incident response teams and can aid in preventing similar incidents in the future.

Finally, event logging is crucial in compliance with regulatory frameworks, such as the General Data Protection Regulation (GDPR) or the Health Insurance Portability and Accountability Act (HIPAA). These regulations require organizations to maintain an audit trail of activities to demonstrate compliance and protect sensitive data.

Event logging provides the necessary evidence to meet these requirements and avoid penalties or legal repercussions.

Implementing a Zero Trust Architecture for Enhanced Security

Implementing Zero Trust involves more than installing a new set of security tools. Essential components include:

Access Control and Identity Management
  • Adopt a Least Privilege Model: Only grant users the minimum access to perform their jobs. Restrict access to sensitive data and resources.
  • Implement Strict Access Controls: Utilize role-based access controls, multi-factor authentication, and robust password management to limit access. Control should be exerted at the network, device, and application levels.
Network Segmentation and Traffic Monitoring
  • Segment the Network: Divide your network into segments and control access between them. This prevents lateral movement in case of a breach. Consider using microsegmentation for more granular control.
  • Log and Inspect All Traffic: Keep a record of all access requests and network traffic. Regularly analyze these logs to detect anomalous behavior and potential threats.
Data Protection and Breach Response
  • Encrypt Data: Ensure data is encrypted in transit and at rest. This adds an extra layer of security, protecting data even if accessed without authorization.
  • Assume Breach: Operate under the assumption that breaches will happen. Have a well-defined plan to quickly detect, respond to, and contain them.
Philosophy and Ongoing Management
  • Adopt a Zero Trust Philosophy: Always verify explicitly and never trust implicitly. Check identity, context, and security posture before granting access.
  • Implement Central Visibility and Control: Manage your zero-trust architecture through a centralized controller to streamline policy enforcement and monitoring.
  • Adopt a Continuous Adaptive Approach: Security is not a one-time setup but an ongoing process. Continuously monitor, learn from, and adapt controls based on emerging threats.

How OMB M-21-31 and M-22-09 Align with Zero Trust Principles

OMB M-21-31 and M-22-09 align with the principles of zero-trust architecture by emphasizing the importance of continuous monitoring, strong authentication, and strict access controls. These directives highlight the need to implement centralized event-logging capabilities, which are essential for promptly detecting and responding to security incidents.

Conclusion

As federal agencies grapple with an increasingly complex cybersecurity landscape, the alignment of OMB directives M-21-31 and M-22-09 with zero-trust principles offers a strategic advantage. These directives are not just isolated policies but are closely aligned with the foundational elements of zero-trust architecture.

For instance, OMB M-21-31 mandates the implementation of centralized event logging and analysis capabilities. This is a core tenet of zero-trust architecture, emphasizing the need for continuous monitoring of all network activities. By centralizing event logs, agencies can detect anomalies and unauthorized access attempts more effectively, enabling prompt response to security incidents.

Similarly, OMB M-22-09 focuses on strong authentication and strict access control. It calls for phishing-resistant multi-factor authentication and for access decisions that consider device and context, in line with the Zero Trust principle of “never trust, always verify.”

Because the two memoranda reinforce each other, an agency that works on them together, for example by feeding identity and device logs into the same central platform that makes access decisions, meets both sets of requirements with less duplicated effort.

The alignment of OMB M-21-31 and M-22-09 with zero-trust principles is not coincidental but a strategic move to bolster the cybersecurity posture of federal agencies. Adhering to these directives, agencies inherently adopt critical aspects of zero-trust architecture, thereby enhancing their resilience against internal and external cyber threats.

References

  1. Office of Management and Budget, Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents, M-21-31, August 27, 2021. https://www.whitehouse.gov/wp-content/uploads/2021/08/M-21-31-Improving-the-Federal-Governments-Investigative-and-Remediation-Capabilities-Related-to-Cybersecurity-Incidents.pdf
  2. Office of Management and Budget, Moving the U.S. Government Toward Zero Trust Cybersecurity Principles, M-22-09, January 26, 2022. https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf
  3. Executive Order 14028, Improving the Nation’s Cybersecurity, May 12, 2021. https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity
  4. Scott Rose, Oliver Borchert, Stu Mitchell and Sean Connelly, Zero Trust Architecture, NIST SP 800-207, August 2020. https://csrc.nist.gov/pubs/sp/800/207/final
  5. Karen Kent and Murugiah Souppaya, Guide to Computer Security Log Management, NIST SP 800-92, September 2006. https://csrc.nist.gov/pubs/sp/800/92/final