ABCDFGHIJKLMNOPQRSTUVWXYZAAABAC
1
IDOriginating DocumentSectionControl TitleNIST SP800-53r5 referencesAssurance LevelRisk Categories
2
1CNSWP v1.0AccessSecrets are injected at runtimeIA-5(7) Authenticator Management | No Embedded Unencrypted Static AuthenticatorsN/AN/A
3
2CNSWP v1.0AccessApplications and workloads are explicitly authorized to communicate with each other using mutual authenticationIA-9 Service Identification and AuthenticationN/AN/A
4
3CNSWP v1.0AccessKeys are rotated frequentlySC-12 Cryptographic Key Establishment and ManagementN/AN/A
5
4CNSWP v1.0AccessKey lifespan is shortSC-12(3) Cryptographic Key Establishment and Management | Asymetric KeyN/AN/A
6
5CNSWP v1.0AccessCredentials and keys protecting sensitive workloads (health/finance/etc) are generated and managed independent of a cloud service providerIA-2(12) Identification and Authentication (Organizational Users) | Acceptance of PIV CredentialsN/AN/A
7
6CNSWP v1.0AccessAuthentication and authorization are determined independently
IA-2(6) Identification and Authentication (Organizational Users) | Access to Accounts - Separate Devices
N/AN/A
8
7CNSWP v1.0AccessAuthentication and authorization are enforced independently
IA-2(6) Identification and Authentication (Organizational Users) | Access to Accounts - Separate Devices
N/AN/A
9
8CNSWP v1.0Accessaccess control and file permissions are updated in real-timeSI-4(2) System Monitoring | Automated Tools and Mechanisms for Real-Time AnalysisN/AN/A
10
9CNSWP v1.0Accessauthorization for workloads is granted based on attributs and roles/permissions previously assignedAC-3(13) Access Enforcement | Attribute-Based Access ControlN/AN/A
11
10CNSWP v1.0AccessABAC and RBAC are usedAC-3(13) Access Enforcement | Attribute-Based Access Control
AC-3(7) Access Enforcement | Role-Based Access Control
N/AN/A
12
11CNSWP v1.0AccessEnd user identity is capable of being accepted, consumed, and forwarded on for contextual or dynamic authorizationSC-7(19) Boundary Protection | Block Communication from Non-Organizationally Configured HostsN/AN/A
13
12CNSWP v1.0AccessAll cluster and workloads operators are authenticatedIA-7 Cryptographic Module AuthenticationN/AN/A
14
13CNSWP v1.0Accesscluster and worklods operate actions are evaluated against access control policies governing context, purpose, and outputIA-7 Cryptographic Module AuthenticationN/AN/A
15
14CNSWP v1.0AccessIdentity federation uses multi-factor authentication
IA-2(1)(2) Identification and Authentication (organizational Users) | Multi-Factor Authenticaiton to Priviledged & Non Priveledged Accounts
N/AN/A
16
15CNSWP v1.0AccessHSMs are used to physically protect cryptographic secrets with an encryption key residing in the HSMAC-4(4) Information Flow Enforcement | Flow Control of Encrypted Information
SC-3(1) Security Function Isolation | Hardware Separation
N/AN/A
17
16CNSWP v1.0AccessSecrets should have a short expiration period or time to liveSI-12 Information Management and RetentionN/AN/A
18
17CNSWP v1.0Accesstime to live and expiration period on secrets is verfied to prevent reuseAC-16(3) Security and Privacy Attributes | Maintenance of Attribute Associations by SystemN/AN/A
19
18CNSWP v1.0Accesssecrets management systems are highly availableSC-12(1) Cryptographic Key Establishment and Management | AvailabilityN/AN/A
20
19CNSWP v1.0Accesslong-lived secrets adhere to periodic rotation and revocationSI-12 Information Management and RetentionN/AN/A
21
20CNSWP v1.0AccessSecrets are distributed through secured communication channels protected commensurate with the level of access or data they are protectingAC-16 Security and Privacy AtributesN/AN/A
22
21CNSWP v1.0AccessSecrets injected are runtime are masqued or dropped from logs, audit, or system dumpsAU-9(3) Protection of Audit Information | Cryptographic ProtectionN/AN/A
23
22CNSWP v1.0ComputeBootstrapping is employed to verify correct physical and logical location of computeSI-7(9) Software, Firmware, and Information Integrity | Verify Boot ProcessN/AN/A
24
23CNSWP v1.0ComputeDisparate data sensitive workloads are not run on the same OS kernelSC-7 Boundary ProtectionN/AN/A
25
24CNSWP v1.0ComputeMonitor and detect any changes to the initial configurations made in runtimeCM-2(2) Baseline Configuration | Automation Support for Accuracy and Currency
CM-3(7) Configuration Change Control | Review System ChangesN/AN/A
26
25CNSWP v1.0ComputeAPI auditing is enabled with a filter for a specific set of API Groups or verbsAU-2 Event LoggingN/AN/A
27
26CNSWP v1.0ComputeContainer specific operating systems are in useCM-2 Baseline Configuration
CM-7 Least FunctionalityN/AN/A
28
27CNSWP v1.0ComputeThe hardware root of trust is based in a Trusted Platform Module (TPM) or virtual TPM (vTPM)SI-7 Software, Firmware, and Information IntegrityN/AN/A
29
28CNSWP v1.0ComputeMinimize administrative access to the control planeAC-6 Least PrivilegeN/AN/A
30
29CNSWP v1.0ComputeObject level and resource requests and limits are controlled through cgroups
SI-7(16) Software, Firmware, and Information Integrity | Time Limit on Process Execution Without Supervision
SI-7(17) Software, Firmware, and Information Integrity | Runtime Application Self-protection
N/AN/A
31
30CNSWP v1.0ComputeSystems processing alerts are periodically tuned for false positivesSI-4(13) System Monitoring | Analyze Traffic and Event PatternsN/AN/A
32
31CNSWP v1.0ComputeAll orchestrator control plane components are configured to communicate via mutual authentication and certificate validation with a periodically rotated certificateAC-3 Access EnforcementN/AN/A
33
32CNSWP v1.0ComputeOnly sanctioned capabilities and system calls (e.g. seccomp filters), are allowed to execute or be invoked in a container by the host operating systemCM-2 Baseline Configuration
CM-7 Least FunctionalityN/AN/A
34
33CNSWP v1.0ComputeChanges to critical mount points and files are prevented, monitored, and alertedCM-5 Access Restrictions for ChangeN/AN/A
35
34CNSWP v1.0ComputeRuntime configuration control prevents changes to binaries, certificates, and remote access configurationsCM-5 Access Restrictions for ChangeN/AN/A
36
35CNSWP v1.0ComputeRuntime configuration prevents ingress and egress network access for containers to only what is required to operateSC-7 Boundary ProtectionN/AN/A
37
36CNSWP v1.0ComputePolicies are defined that restrict communications to only occur between sanctioned microservice pairsSC-7 Boundary ProtectionN/AN/A
38
37CNSWP v1.0ComputeUse a policy agent to control and enforce authorized, signed container imagesCM-5 Access Restrictions for ChangeN/AN/A
39
38CNSWP v1.0ComputeUse a policy agent to control provenance assurance for operational workloadsCM-5 Access Restrictions for ChangeN/AN/A
40
39CNSWP v1.0ComputeUse a service mesh that eliminates implicit trust through data-in-motion encryption (data in transit)SC-7 Boundary ProtectionN/AN/A
41
40CNSWP v1.0ComputeUse components that detect, track, aggregate and report system calls and network traffic from a containerSI-4 System MonitoringN/AN/A
42
41CNSWP v1.0ComputeWorkloads should be dynamically scanned to detect malicious or insidious behavior for which no known occurrence yet existsSI-3 Malicious Code ProtectionN/AN/A
43
42CNSWP v1.0ComputeEnvironments are continuously scanned to detect new vulnerabilities in workloadsRA-5 Vulnerability Monitoring and ScanningN/AN/A
44
43CNSWP v1.0ComputeActionable audit events are generates that correlate/contextualize data from logs into "information" that can drive decision trees/incident responseAU-3 Content of Audit RecordsN/AN/A
45
44CNSWP v1.0Computesegregation of duties and the principle of least privilege is enforcedAC-6 Least PrivilegeN/AN/A
46
45CNSWP v1.0ComputeNon-compliant violations are detected based on a pre-configured set of rules that filter violations of the organization's policiesSI-7 Software, Firmware, and Information IntegrityN/AN/A
47
46CNSWP v1.0ComputeNative secret stores encrypt with keys from an external Key Management Store (KMS)SC-12(3) Systems & Communication ProtectionN/AN/A
48
47CNSWP v1.0ComputeNative secret stores are not configured for base64 encoding or stored in clear-text in the key-value store by defaultSC-12(3) Systems & Communication ProtectionN/AN/A
49
48CNSWP v1.0ComputeNetwork traffic to malicious domains is detected and deniedSI-4 System MonitoringN/AN/A
50
49CNSWP v1.0ComputeUse encrypted containers for sensitive sources, methods, and dataSC-28 Protection of Information at RestN/AN/A
51
50CNSWP v1.0ComputeUse SBOMs to identify current deployments of vulnerable libraries, dependencies, and packagesCM-8 System Component InventoryN/AN/A
52
51CNSWP v1.0ComputeProcesses must execute only functions explicitly defined in an allow listCM-2 Baseline Configuration
CM-7 Least FunctionalityN/AN/A
53
52CNSWP v1.0ComputeFunctions are not be allowed to make changes to critical file system mount pointsCM-5 Access Restrictions for ChangeN/AN/A
54
53CNSWP v1.0ComputeFunction access is only permitted to sanctioned servicesCM-2 Baseline Configuration
CM-7 Least FunctionalityN/AN/A
55
54CNSWP v1.0ComputeEgress network connection is monitored to detect and prevent access to C&C (command and control) and other malicious network domainsSI-4 System MonitoringN/AN/A
56
55CNSWP v1.0ComputeIngress network inspection is employed detect and remove malicious payloads and commandsSI-4 System MonitoringN/AN/A
57
56CNSWP v1.0ComputeServerless functions are run in tenant-based resource or performance isolation for similar data classificationsSC-7(21) Boundary Protection | Isolation of System ComponentsN/AN/A
58
57CNSWP v1.0Deploytrust confirmation verifies the image has a valid signature from an authorized sourceSR-4 (3) PROVENANCE | VALIDATE AS GENUINE AND NOT ALTERED
SR-4 (4) PROVENANCE | SUPPLY CHAIN INTEGRITY — PEDIGREE
N/AN/A
59
58CNSWP v1.0DeployImage runtime policies are enforced prior to deployment
SI-7 (17) SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITY | RUNTIME APPLICATION SELF-PROTECTION
N/AN/A
60
59CNSWP v1.0DeployImage integrity and signature are verifying prior to deploymentSR-4 (3) PROVENANCE | VALIDATE AS GENUINE AND NOT ALTERED
SR-4 (4) PROVENANCE | SUPPLY CHAIN INTEGRITY — PEDIGREE
N/AN/A
61
60CNSWP v1.0DeployApplications provide logs regarding authentication, authorization, actions, and failuresCM-3 CONFIGURATION CHANGE CONTROLN/AN/A
62
61CNSWP v1.0DeployForensics capabilities are integrated into an incident response plan and proceduresINCIDENT HANDLING | MALICIOUS CODE AND FORENSIC ANALYSISN/AN/A
63
62CNSWP v1.0DeployAI, ML, or statistical modeling are used for behavioural and heuristic environment analysisSI-3 SYSTEM AND INFORMATION INTEGRITYN/AN/A
64
63CNSWP v1.0DevelopEstablish a dedicated Production environmentSA-3(1) SYSTEM DEVELOPMENT LIFE CYCLE | MANAGE PREPRODUCTION ENVIRONMENTN/AN/A
65
64CNSWP v1.0DevelopLeverage Dynamic deploymentsSA-8(31) SECURITY AND PRIVACY ENGINEERING PRINCIPLES | SECURE SYSTEM MODIFICATIONN/AN/A
66
65CNSWP v1.0DevelopIntegrate vulnerability and configuration scanning in the IDE or at the pull requestSA-11(1) DEVELOPER TESTING AND EVALUATION | STATIC CODE ANALYSISN/AN/A
67
66CNSWP v1.0DevelopEstablish dedicated development, testing, and production environmentSA-15 DEVELOPMENT PROCESS, STANDARDS, AND TOOLSN/AN/A
68
67CNSWP v1.0DevelopBuild tests for business-critical codeSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
69
68CNSWP v1.0DevelopBuild tests for business-critical infrastructureSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
70
69CNSWP v1.0DevelopTest suite able to be ran locallySA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
71
70CNSWP v1.0DevelopTest suites should be available to run in a shared environmentSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
72
71CNSWP v1.0DevelopImplement two non-author reviewers/approvers prior to mergingSA-11(4) DEVELOPER TESTING AND EVALUATION | MANUAL CODE REVIEWSN/AN/A
73
72CNSWP v1.0DevelopCode should be clean and well commentedN/AN/A
74
73CNSWP v1.0DevelopFull infrastructure tests are usedSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
75
74CNSWP v1.0DevelopRegression tests are usedSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
76
75CNSWP v1.0DevelopTest suites are updated against new and emerging threats and developed into security regressions testsSA-11 DEVELOPER TESTING AND EVALUATIONN/AN/A
77
76CNSWP v1.0DevelopEstablish a dedicated Testing environmentSA-3(1) SYSTEM DEVELOPMENT LIFE CYCLE | MANAGE PREPRODUCTION ENVIRONMENTN/AN/A
78
77CNSWP v1.0DevelopContinuous integration server is isolatedSC-39 PROCESS ISOLATIONN/AN/A
79
78CNSWP v1.0DevelopUse threat model results to determine ROI for test development
SA-11(2) DEVELOPER TESTING AND EVALUATION | THREAT MODELING AND VULNERABILITY ANALYSES
N/AN/A
80
79CNSWP v1.0DistributeTrust is verifiedN/AN/A
81
80CNSWP v1.0DistributeArtifacts ready for deployment are managed in a staging or pre-prod registryN/AN/A
82
81CNSWP v1.0Distributecontainer images are hardened following best practicesN/AN/A
83
82CNSWP v1.0DistributeStatic application security testing (SAST) is performedN/AN/A
84
83CNSWP v1.0DistributeTest suites follow the test pyramidN/AN/A
85
84CNSWP v1.0DistributeArtifacts undergoing active development are held in a private registeryN/AN/A
86
85CNSWP v1.0DistributeScan application manifests in CI pipelineRA-5 VULNERABILITY MONITORING AND SCANNINGN/AN/A
87
86CNSWP v1.0DistributeCI server's for sensitive workloads are isolated from other workloadsSC-39 PROCESS ISOLATIONN/AN/A
88
87CNSWP v1.0DistributeBuilds requiring elevated privileges must run on dedicated serversSC-39 PROCESS ISOLATIONN/AN/A
89
88CNSWP v1.0DistributeBuild policies are enforced on the CI pipelineSA-1 POLICY AND PROCEDURESN/AN/A
90
89CNSWP v1.0DistributeSign pipeline metadataSI-7 SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITYN/AN/A
91
90CNSWP v1.0DistributeBuild stages are verified prior to the next stage executingSI-7 SOFTWARE, FIRMWARE, AND INFORMATION INTEGRITYN/AN/A
92
91CNSWP v1.0DistributeImages are scanned within the CI pipelineRA-5 VULNERABILITY MONITORING AND SCANNING
SA-3 SYSTEM DEVELOPMENT LIFE CYCLE
N/AN/A
93
92CNSWP v1.0DistributeVulnerability scans are coupled with pipeline compliance rulesSA-1 POLICY AND PROCEDURESN/AN/A
94
93CNSWP v1.0DistributeDynamic application security testing (DAST) is performedSA-11 (8) & (9) INTERACTIVE APPLICATION SECURITY TESTINGN/AN/A
95
94CNSWP v1.0DistributeApplication instrumentation is employedSI-4 SYSTEM MONITORINGN/AN/A
96
95CNSWP v1.0DistributeAutomated test results map back to requirementsN/AN/A
97
96CNSWP v1.0DistributeInfrastructure security tests must be employedN/AN/A
98
97CNSWP v1.0DistributeTests to verify the security health are executed at time of build and at time of deploySI-4 SYSTEM MONITORINGN/AN/A
99
98CNSWP v1.0DistributeIaC is subject to the same pipeline policy controls as application codeN/AN/A
100
99CNSWP v1.0DistributeSecurity testing is automatedSA-11 DEVELOPER TESTING AND EVALUATION
CA-8 PENETRATION TESTING
N/AN/A