Requires software and its documentation to be used within contract and copyright terms, use of quantity licensed software to be tracked so copying and distribution stay controlled, and peer to peer file sharing to be controlled and documented so it cannot be used to distribute copyrighted work.
What else in your programme already covers this
This control maps to 36 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
5.2.1 An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are not at risk from malware
5.2.2 The deployed anti-malware solution(s): • Detects all known types of malware. • Removes, blocks, or contains all known types of malware
6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval
You are reading one control. How much of NIST SP 800-53 Rev 5 have you already done?
NIST SP 800-53 Rev 5 NIST800-CM-10 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-53 Rev 5 your existing evidence covers. Hold ISO 27001:2022 and 163 of 300 NIST SP 800-53 Rev 5 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. 342 were rejected on the ISO 27001:2022 pair alone.