What Compliance Means Today

Pubblicato:
significato di compliance compliance aziendale ambiti compliance evidenze audit governance aziendale +3
What Compliance Means Today

Compliance is not a folder of policies: it’s the ability to demonstrate, over time, that regulatory requirements and internal rules were actually applied, by named people, with verifiable evidence and tamper-evident trails.

This article is practical, not legal. It explains compliance from the perspective of those who must build processes that stand up to auditors and regulators, separating three often-confused elements: the written rule, the executed control, and the evidence that proves execution.

Compliance as continuous proof

What auditors look for is reconstructability. It’s easy to produce a policy signed last week; it’s harder to show who removed an administrator’s access three months ago, when they did it, and which approval authorized the action. Without that chain—requirement, owner, dated evidence, audit trail—the control effectively does not exist for audit purposes.

Regulation and oversight are expanding: directives such as NIS2 and DORA, together with data protection rules like the GDPR and standard frameworks (ISO families), require organizations to prove that controls are operational, not just documented. The result is that a broader set of organizations—beyond large enterprises—must be able to demonstrate controls month after month.

Operational rule: if you cannot name the date, the responsible person and a verifiable artifact for a key control, that control is an intention, not compliance.

Document owned vs. execution proved

A policy shows someone decided on a rule. Execution proves the rule was followed. The chain that makes a control defensible is:

  • applicable requirement
  • control design and frequency
  • designated owner
  • dated evidence with a unique identifier
  • an immutable audit trail
  • logged findings and remediation with independent verification

A quick self-check you can do without tools: pick a key control (e.g., quarterly review of privileged accounts) and ask for the last execution details—date, executor, exported file or register, approving signature. If you can’t get those in minutes, the problem is not the policy.

Where compliance applies: privacy, security, governance and more

Although legal references differ by country and sector, the same method applies. Below are common domains, their objectives, typical references and the minimum evidence auditors will expect.

  • Privacy — Objective: protect personal data; Reference: GDPR and local guidance; Evidence: processing register, DPIAs with owner and date, breach register.
  • ICT Security — Objective: ensure system resilience and incident response; Reference: NIS2, DORA for financial entities, ISO/IEC 27001; Evidence: incident register with timestamps, resilience test results, supplier inventory.
  • Governance and misconduct prevention — Objective: prevent/monitor organizational risks; Reference: national corporate governance models and internal codes; Evidence: minutes of oversight bodies, information flows, action plans with owners.
  • Whistleblowing and internal reporting — Objective: confidential handling of reports; Reference: applicable whistleblower rules; Evidence: intake and handling log, outcomes and timelines.
  • AI systems governance — Objective: inventory and human oversight for AI; Reference: AI Act (EU) and organizational policies; Evidence: systems inventory, risk classification, human review records.

Different references, same question: which obligation applies, which control enforces it, who owns it, and what evidence proves it.

The evidence chain: policy, control, owner, proof

Take a quarterly privileged access review. The policy sets the frequency. The executed control is the review with identified accounts and any revocations. The owner is the person accountable (e.g., HR or IT manager). The evidence is a dated export with a unique ID and an approval record. If any link is missing, auditors will treat the control as not implemented.

Confusing policy with execution is a frequent cause of findings: policies are easy to draft; preserving evidence consistently is harder.

Audit checklist for each control:

  • What requirement does this cover? (policy with version and date)
  • How is the control performed and how often? (procedure or config)
  • Who owns it and what is the delegation? (named owner with formal delegation)
  • What dated evidence exists? (file/export with source and ID)
  • Is there an immutable audit trail? (who changed/approved what and when)
  • Are findings logged with severity and owner? (non-conformities register)
  • Is remediation tracked and verified by an independent function? (closure evidence)

With NIS2, DORA and similar regimes, supervisors increasingly ask for proof that controls are operational—mere publication of a policy is no longer sufficient.

Three distinctions auditors often mix up

  • Authorized exception: a temporary, documented exception with justification, owner and explicit expiration; not a non-conformity while valid.
  • Non-conformity (finding): a deviation that must be recorded, assigned, remediated and independently verified closed.
  • Incident: an operational or security event with its own lifecycle and notification requirements; it may create findings but is not synonymous with one.

An exception without expiration is simply an unresolved finding in disguise.

Software can collect, version and link evidence and reduce reconstruction work, but assessing the adequacy of a control remains a human responsibility. AuditReady helps collect and centralize evidence, make documents tamper-evident, track critical operations and manage findings and remediations, but it does not replace legal assessments or the client’s judgement.

Roles, segregation and third-party controls

A defensible control separates four functions:

  • Proposer (process owner) — identifies the need and risks.
  • Approver (senior manager) — accepts residual risk or grants exceptions.
  • Executor (operational owner) — carries out the control and produces evidence.
  • Verifier (independent function) — validates execution (internal audit, DPO, compliance or oversight body).

Example: IT schedules backups and retains logs (executor), the data protection officer verifies the backups align with processing records (verifier), and the relevant manager approves any temporary exceptions for restore tests.

Outsourcing does not transfer accountability. Contracts define obligations; you still must qualify, monitor and obtain dated evidence from suppliers. Regulations such as DORA add explicit requirements for managing third‑party ICT risk and supervising critical suppliers.

What to request from a supplier:

  • A dated attestation with a stated validity period (not just an issue date).
  • Results and scope of the last resilience or restoration test.
  • The incident register entries relevant to the service, with response times.
  • Open remediation plans with owners and deadlines.

Each document should be linked to: service, risk, requirement, responsible person, expiration and the evidence itself. When evidence and verification are combined in one view, supplier control becomes continuous rather than a periodic scramble.

Incident notification: an operational sequence

Incident handling is a timed process. When an outage or possible data exposure occurs, the important questions are: who assessed significance, who decided escalation, who notified which authority and when, and where are those records?

Under many regimes implementing NIS2, organizations classified as essential or important must provide an initial notification without undue delay and, where possible, within 24 hours of becoming aware; a full notification typically follows within 72 hours. GDPR breach notifications to data protection authorities are generally expected within 72 hours from awareness, where applicable. Exact obligations depend on the entity classification and the services affected and must be defined before an incident occurs.

Evidence an auditor will expect for incidents:

  • detection timestamp and initial qualification
  • decision to escalate and name of the notifier
  • notifications sent (recipients and timestamps)
  • containment actions, root cause and closure verification

If the decision to notify is not documented, auditors will consider it as not taken.

Common mistakes that weaken audits

Typical problems that break the evidentiary chain:

  • Controls without a named owner.
  • Series of open-ended exception renewals with no fresh approval.
  • Evidence scattered across emails, chats and shared folders without unique IDs.
  • Findings closed by the same team that fixed them, with no independent verification.
  • Screenshots or messages with no date or source that cannot be placed in time.

Remember: certifications and one-time assessments capture a snapshot; compliance must be demonstrated continuously. Tools help collect and protect evidence, but governance and human review are essential. If AI is used in compliance workflows, it must be inventoried, its role bounded and human sign-off required for significant decisions.

Pre-audit checklist: seven questions to answer now

For one key control per domain, answer these questions. Any negative answer should be logged as a finding and managed—don’t just annotate your policy.

  1. Does the policy or requirement show version and approval date?
  2. Is an owner named with formal delegation?
  3. Is the last execution dated and tied to a uniquely identifiable artifact?
  4. Is there an immutable audit trail that records changes and approvals?
  5. Are exceptions documented with justification, owner and expiry, and not repeatedly renewed without new approval?
  6. Are findings recorded with severity, owner, deadline and remediation plan?
  7. Is remediation closure verified by a function independent from the fixer?

If you answer no to any question, open a finding, assign it and set a deadline. AuditReady’s checklist of evidence (https://audit-ready.eu/en/tools/checklist-evidences-audit) and incident deadline calculator (https://audit-ready.eu/en/tools/incident-deadline-calculator) can help you design procedures and calculate notification windows before an incident occurs.

Close the loop with an Audit Day Pack: for management, a concise package that lists each control, its state, owner, next due date and direct link to evidence. AuditReady centralizes controls, evidence, findings and the Audit Day Pack so that the context is available when it’s needed; the final evaluation, however, remains a human activity.

FAQs on operational compliance

Q: Is an approved policy enough to prove compliance? A: No—approval shows intent. You must show the control was executed during the relevant period with owner, date and verifiable evidence.

Q: Can exceptions be renewed? A: Only with a new approval, updated justification and a fresh expiry date. Repeated renewals without reassessment are a finding.

Q: When does an exception become a non‑conformity? A: When it expires without authorization, when compensating controls were not performed, or when the scope changes without reassessment.

Q: Is a supplier’s certification sufficient evidence? A: Not on its own. You need dated attestations that cover the service in use and periodic verification that the attestations remain valid.

Q: How to handle evidence from chats? A: Move it into the evidence registry, assign date, source, owner and unique ID; keep the original message as an attachment and link it to the relevant control.

If you are still reconstructing evidence manually before each review, centralizing controls, owners, expiries and evidence will save time and make the audit defensible. Request a demo to see an Audit Day Pack and how AuditReady supports evidence centralization and tamper-evident trails: https://audit-ready.eu/?lang=en.

AuditReady supports the compliance process—it collects and links evidence, preserves immutability, tracks findings and records verifications—while leaving legal interpretation and final decisions to your organization’s accountable functions.