Knowesis and Stratom Achieve CMMC Level 2 Certification for Defense Cybersecurity
Article Content
- •Knowesis achieved CMMC Level 2 certification on September 11, 2026.
- •Stratom announced its CMMC Level 2 compliance on September 15, 2026.
- •Both companies meet the 110 security requirements outlined in NIST SP 800-171 Revision 2.
Knowesis and Stratom have both achieved Cybersecurity Maturity Model Certification (CMMC) Level 2, confirming their compliance with the 110 security requirements in NIST SP 800-171 Revision 2 for protecting Controlled Unclassified Information (CUI). Knowesis completed its certification on September 11, 2026, ahead of the Department of War's review of the CMMC program, positioning itself as a trusted partner for federal agencies. Stratom announced its compliance on September 15, 2026, highlighting its commitment to safeguarding sensitive information and supporting defense program requirements. Both companies emphasize the importance of cybersecurity in the defense sector and the need for extensive documentation and third-party assessments to achieve this certification. The CMMC framework is crucial for organizations handling CUI, especially in light of ongoing cybersecurity threats.
Ask AI about this cluster
Answers cite the sources they use
Timeline
More articles in this cluster (2)
Continue Reading
Critical Cisco FMC Vulnerabilities Under Active Exploitation Cisco's Secure Firewall Management Center (FMC) Software has two critical vulnerabilities, CVE-2026-20079 and CVE-2026-20316, that are currently being exploited by state-sponsored and ransomware actors. CVE-2026-20079, rated 10.0 on the CVSS scale, allows unauthenticated remote attackers to bypass authentication and…
Critical Zero-Day Vulnerability in Cisco Secure Email Gateway Exploited On September 14, 2026, Cisco disclosed a critical SQL injection vulnerability (CVE-2026-76461) in its Secure Email Gateway, allowing unauthenticated remote attackers to execute arbitrary commands with root privileges. This vulnerability arises from insufficient validation in the email parsing logic. Cisco confirmed…