EvidenceSheet
NIST SP 800-53 Rev 5 · PM - Program Management

PM-14 Testing, Training, and Monitoring

a. Implement a process for ensuring that organizational plans for conducting security and privacy testing, training, and monitoring activities associated with organizational systems: 1. Are developed and maintained; and 2. Continue to be executed; and b. Review testing, training, and monitoring plans for consistency with the organizational risk management strategy and organization-wide priorities for risk response actions.

Source: NIST SP 800-53 Rev 5, PM-14. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

9
artefacts
0
held by a system
2
at each review
hard
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Results of risk assessments associated with conducting security and privacy testing, training, and monitoring activities · HR system / LMS
  • Test of Organizational processes for the development and maintenance of plans for conducting security and privacy testing, training, and monitoring activities; mechanisms supporting the development and maintenance of plans for conducting security and privacy testing, training, and monitoring activities · HR system / LMS

governing documentDocuments that govern the control

  • Information security program plan · Policy repository / GRC workspace
  • Privacy program plan · Policy repository / GRC workspace
  • Plans for conducting security and privacy testing, training, and monitoring activities · HR system / LMS
  • Organizational procedures addressing the development and maintenance of plans for conducting security and privacy testing, training, and monitoring activities · HR system / LMS
  • Risk management strategy · Document repository
  • Procedures for the review of plans for conducting security and privacy testing, training, and monitoring activities for consistency with risk management strategy and risk response priorities · HR system / LMS
  • Documentation of the timely execution of plans for conducting security and privacy testing, training, and monitoring activities · HR system / LMS

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

PM-13 Security and Privacy Workforce · PM-15 Security and Privacy Groups and Associations