A formal disciplinary process is to be established and made known so that action can be taken against staff and relevant outside parties who break the security policy. Purpose: make sure people understand the consequences of breaching the policy, deter breaches and deal properly with those who commit them. Guidance: disciplinary action should start only after it has been verified that a violation actually occurred (5.28). The process provides a graduated response that weighs the nature of the breach (who, what, when, how), its seriousness and consequences; whether it was deliberate and malicious or accidental; whether it is a first or repeat offence; and whether the person had been properly trained. The response also accounts for legal, regulatory, contractual and business requirements and other relevant factors. The process doubles as a deterrent against breaching the policy, topic-specific policies and procedures, and deliberate violations may call for immediate action. Other information: where possible, protect the identity of people subject to disciplinary action in line with applicable requirements; consider rewarding people who show excellent security behaviour.
This control maps to 18 controls across 16 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
ISO 27002:2022 6.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 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. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 18 it maps to, and the evidence behind each claim, over MCP and REST.