Leverage Vetted Modules or Services for Application Security Components
Description
Leverage vetted modules or services for application security components, such as identity management, encryption, and auditing and logging. Using platform features in critical security functions will reduce developersā workload and minimize the likelihood of design or implementation errors. Modern operating systems provide effective mechanisms for identification, authentication, and authorization and make those mechanisms available to applications. Use only standardized, currently accepted, and extensively reviewed encryption algorithms. Operating systems also provide mechanisms to create and maintain secure audit logs.
Implementation Checklist
Tool Recommendations
Developer-first application security with SCA, container scanning, IaC security, and SAST integrated into CI/CD
Snyk · Per-developer subscription
Application security testing suite with SAST (Coverity), SCA (Black Duck), and DAST for comprehensive AppSec
Synopsys · Per-developer subscription
Cloud-native application security platform with SAST, SCA, DAST, API security, and supply chain security testing
Checkmarx · Per-developer subscription
Threats & Vulnerabilities (CIS RAM)
Threat Scenarios
Broken Custom Cryptography Implementation
ConfidentialityA developer implements a custom encryption algorithm instead of using a vetted cryptographic library, and the implementation contains fundamental flaws that allow attackers to decrypt sensitive data.
Authentication Bypass in Custom Identity Management Module
ConfidentialityA home-built authentication system contains logic flaws that allow attackers to bypass login because the developers built it from scratch instead of leveraging a vetted identity management framework.
Audit Log Tampering Due to Custom Logging Implementation
IntegrityAn attacker modifies custom-built audit logs to cover their tracks because the application uses a bespoke logging system with no integrity protections instead of a vetted, tamper-evident logging framework.
Vulnerabilities (When Safeguard Absent)
Custom-Built Security Components Instead of Vetted Modules
Developers building custom implementations of security-critical functions such as encryption, authentication, and logging instead of using proven libraries are far more likely to introduce exploitable implementation flaws.
Inconsistent Security Component Quality Across Applications
Without standardizing on vetted modules for security functions, each application implements these capabilities differently, creating inconsistent quality and unpredictable security properties.
Evidence Requirements
| Type | Evidence Item | Collection Frequency |
|---|---|---|
| Technical | Configuration screenshots or exports showing protection controls enabled | Captured quarterly |
| Document | Procedure documentation for protection measures | Reviewed annually |
| Technical | Encryption configuration evidence (disk encryption status, TLS settings) | Scanned monthly |
| Document | Key management procedures and key rotation records | Reviewed annually |
| Technical | SIEM dashboard showing log sources and collection status | Captured monthly |
| Record | Log review records and findings | Per review cycle |
| Document | Governing policy document (current, approved, communicated) | Reviewed annually |