Skip to content

Secrecy, Verification Suppression & Commitment Escalation

Secrecy, verification suppression and commitment escalation reduce the target’s access to checking, consultation or withdrawal. The attacker may frame a matter as confidential, limit the information available, discourage independent confirmation, re-engage after refusal, test boundaries through small requests, or use prior involvement to make disengagement more difficult.

Legitimate confidentiality should still allow verification, escalation and recordkeeping through an appropriately restricted organisational pathway. Prior involvement, sunk cost, embarrassment, or a sense of special responsibility should not determine whether the next action is authorised.

This tactic can be assessed by asking:

  • What consultation, context, verification, or reporting path is being restricted?
  • What earlier action, investment, or relationship is being used to sustain involvement?
  • Is the target being made uniquely responsible or discouraged from seeking another view?
  • What restricted but independent escalation path remains available?

Secrecy, Verification Suppression & Commitment Escalation includes the techniques below. Select a technique to open its behavioural method, common examples, relevant taxonomy boundaries, and control-domain orientation in the Technique Catalogue.


Secrecy, verification suppression, and commitment escalation activity may involve one or more of the following behaviours:

Secrecy and confidentiality framing

  • requesting confidentiality, discretion, secrecy, or restricted handling
  • framing the interaction as “off the record”, “between us”, “restricted”, “private”, or “need to know”
  • making normal escalation feel like betrayal, disloyalty, delay, incompetence, or breach of trust
  • claiming that only a small number of people are allowed to know about the request
  • presenting confidentiality as a reason to avoid normal workflow, recordkeeping, callback, or approval

Commitment and prior-involvement behaviour

  • starting with low-risk or harmless requests before escalating to sensitive action
  • repeatedly re-engaging the target to sustain familiarity, momentum, or compliance
  • testing boundaries through small policy exceptions before larger requests
  • making the target feel uniquely trusted, selected, responsible, or personally important

Pressure and suppression

  • discouraging independent verification, callbacks, second-person review, or escalation
  • withholding context or selectively revealing information to shape the target’s decision
  • increasing pressure after hesitation, delay, refusal, or attempted verification
  • using what the target has already done, paid, shared, approved, or broken a rule, to argue they cannot now stop, withdraw, or report
  • pairing secrecy with urgency, fear, guilt, affection, authority, or insider framing
  • asking for money, credentials, access, file sharing, supplier changes, approval, or information disclosure after trust has already been built