Going Hard on Software: OMB Unveils Mandatory Software Supply Chain Security Compliance Requirements
Client Alert | 2 min read | 09.15.22
Yesterday, the Office of Management and Budget (OMB) released Memorandum M-22-18, implementing software supply chain security requirements that will have a significant impact on software companies and vendors in accordance with Executive Order 14028, Improving the Nation’s Cybersecurity. The Memorandum requires all federal agencies and their software suppliers to comply with the NIST Secure Software Development Framework (SSDF), NIST SP 800-218, and the NIST Software Supply Chain Security Guidance whenever third-party software is used on government information systems or otherwise affects government information. The term “software” includes firmware, operating systems, applications, and application services (e.g., cloud-based software), as well as products containing software. It is critical to note that these requirements will apply whenever there is a major version update or new software that the government will be using.
The Memorandum requires agencies to take the following actions:
- within 90 days, agencies must inventory all software subject to the Memorandum;
- within 120 days, agencies will have developed a process to communicate requirements to vendors and ensure that vendor attestation letters can be collected in a central agency system;
- within 180 days, agencies must assess training needs and develop plans for the review and validation of attestation documents;
- within 270 days for critical software and within 365 days for all others, agencies will require self-attestations from all software producers; and
- as needed, obtain from software producers a Software Bill of Materials (SBOM)or other artifact(s) that demonstrate conformance to secure software development practices.
To comply with the Memorandum, software producers must attest that they adhere to the NIST software supply chain frameworks and guidance. In lieu of a self-attestation, software producers may also submit third-party assessments of compliance with the software security standards conducted by a certified FedRAMP assessor or an assessor approved by the agency.
Software producers or vendors providing software to the federal government should begin reviewing their security practices and their overall software development lifecycle immediately to ensure that they can attest to compliance with the applicable NIST standards in the very near future.
Contacts
Senior Counsel
She/Her/Hers
Insights
Client Alert | 7 min read | 08.16.24
Over the past several years, federal courts have increasingly questioned the authority of administrative law judges (ALJs) to adjudicate alleged violations of certain labor and employment statutes. In the last several weeks, two U.S. district courts in Texas issued decisions halting unfair labor practice proceedings before the National Labor Relations Board (NLRB) on the grounds that NLRB ALJs lack the constitutional authority to preside over such actions due to unconstitutional protections against their removal.[1] Similarly, the last year has seen several decisions by courts in the Fifth and Eleventh Circuits finding that ALJs, whose decisions are not reviewable by a Presidential appointee, lack constitutional authority under the Appointments Clause to adjudicate claims.[2] The trend illustrated by these decisions, combined with the Supreme Court’s decision in June to abandon the Chevron doctrine of extending deference to federal agency rule-making proceedings, portend significant changes in the way employers interact with federal agencies that enforce labor and employment law.
Client Alert | 2 min read | 08.15.24
Department of Defense Plans Increased Investment in Clean Energy
Client Alert | 7 min read | 08.15.24
