Chapter 10 of 19

10. Exceptions and Constraints

DACS permits constrained-use exceptions, but exceptions must be explicit and evidenced. An exception does not make a failed control pass. It allows bounded use under recorded authority and conditions.

Each exception record shall include:

  • control ID or Gate condition affected;
  • reason for exception;
  • decision scope and usage boundary;
  • risk or constraint statement;
  • approving authority or approved exception rule reference;
  • readiness state;
  • expiration or review condition;
  • remediation owner and next action where applicable.

An approved constrained-use exception that permits material use shall produce Caution, not Proceed, and every failed control remains Fail. If use is prohibited, the Gate readiness state shall be Stop. Candidate or unresolved evidence that is not permitted for material reliance shall remain Quarantined until the applicable rules establish another state.

Back to document overview

DACS Strategic Insights

Direct, zero-fluff updates on DACS controls, defensibility practices, and framework releases.

By subscribing, you’re asking DataVaultAlliance to send you DACS controls, defensibility practices, and framework releases. You can unsubscribe at any time. See our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy
and Terms of Service apply.

Access This DACS Document

Verify your email to access the document. No account or password is required. You may need to verify again if you change devices, use private browsing, or clear your cookies.

We will use your email to provide access to the requested document. Marketing communications are optional.