Objective 5.4 covers the elements of effective security compliance: meeting the laws, regulations, standards, and contracts that apply to you and being able to prove it, plus the privacy concepts that drive much of it.
Reporting and consequences. Compliance reporting can be internal, to your own leaders, or external, to outside parties. The consequences of non-compliance are fines (money), sanctions (penalties such as an order to stop processing), reputational damage, loss of license, and contractual impacts, which a contract partner imposes rather than a regulator.
Monitoring. You check controls regularly, collect evidence, and fix gaps before an auditor finds them. Due diligence is investigating and understanding, while due care is acting on what you learned with sensible, consistent protections. An attestation is a written statement that controls were in place and operated, while an acknowledgement states that a person read or agreed to a rule. Monitoring can be internal or external, and automation catches problems earlier but checks only what it is configured to check.
Privacy. Privacy law operates at local or regional, national, and global levels. A data subject is the identifiable person the data is about. The controller decides why and how data is processed, and the processor acts on the controller's behalf. Data ownership sets who is accountable for personal data and decides how it is used, apart from who stores or processes it. Organizations need a data inventory and retention rules, because you cannot protect or delete what you do not know you hold, and the right to be forgotten lets people ask for deletion, with exceptions.
Exam questions describe a regulator, a fine, or a data request and ask for the matching concept, such as internal versus external reporting, attestation, data subject rights, or controller versus processor.
Written by Knotch · reviewed Nov 15, 2026 · 3 study articles behind this page