Train personnel to perform the specific information security duties and responsibilities assigned to their roles.
What else in your programme already covers this
This control maps to 93 controls across 32 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
4.1.1 All security policies and operational procedures that are identified in Requirement 4 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
4.1.2 Roles and responsibilities for performing activities in Requirement 4 are documented, assigned, and understood
5.1.2 Roles and responsibilities for performing activities in Requirement 5 are documented, assigned, and understood
6.1.2 Roles and responsibilities for performing activities in Requirement 6 are documented, assigned, and understood
6.2.2 Software development personnel working on bespoke and custom software are trained at least once every 12 months as follows: • On software security relevant to their job function and development languages. • Including secure
7.1.1 All security policies and operational procedures that are identified in Requirement 7 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
7.1.2 Roles and responsibilities for performing activities in Requirement 7 are documented, assigned, and understood
9.1.1 All security policies and operational procedures that are identified in Requirement 9 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
9.1.2 Roles and responsibilities for performing activities in Requirement 9 are documented, assigned, and understood
3.1.1 All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
3.1.2 Roles and responsibilities for performing activities in Requirement 3 are documented, assigned, and understood
8.1.1 All security policies and operational procedures that are identified in Requirement 8 are: • Documented. • Kept up to date. • In use. • Known to all affected parties
NIST800-PM-14 Testing, Training, and Monitoring. Implement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems: Are developed and maintained; and Continue to be
NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced
NIST-CSF-PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
NIST-CSF-PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
You are reading one control. How much of CMMC 2.0 have you already done?
CMMC 2.0 AT.L2-3.2.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CMMC 2.0 your existing evidence covers. Hold FedRAMP Moderate and 108 of 110 CMMC 2.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 1 were rejected on the FedRAMP Moderate pair alone.