Skip to content

Authority & Obligation Pressure

Authority and obligation pressure uses hierarchy, seniority, official standing, duty, compliance expectations, delegated authority, or claimed power over consequences to influence action. The requester may hold real authority, invoke someone else’s authority, or fabricate it, but the pressure comes from the perceived cost of questioning or refusing.

A title, legal reference, policy claim, reporting line, or statement of responsibility can make an unsafe action feel mandatory. Genuine authority can also be misused where the requester is compromised, mistaken, acting outside scope, or pressing for an action that has not followed the required decision path.

Authority and obligation pressure can be assessed by asking:

  • What authority, duty, approval, or consequence is being invoked?
  • What action is being pressured or accelerated?
  • Does the requester have authority for this specific action and scope?
  • What verification, approval, or escalation path remains applicable?

Authority & Obligation Pressure 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.


Authority and obligation pressure activity may involve one or more of the following behaviours:

Authority and role presentation

  • invoking seniority, rank, title, official status, legal status, regulatory power, or specialist expertise
  • claiming to represent an executive, manager, board member, regulator, auditor, legal function, HR function, government agency, law enforcement body, supplier authority, or delegated approver
  • using formal, demanding, legalistic, disciplinary, or compliance-oriented language
  • using a cloned voice, a deepfake video likeness, or AI-generated correspondence so the seniority or official status appears authentically present
  • presenting a forged notice, legal letter, audit demand, or official letterhead as proof of authority
  • presenting the request as a direct instruction, escalation, formal requirement, or executive priority
  • implying that the requester has authority to override normal process

Request and workflow behaviour

  • asking for payment, supplier change, payroll change, credential reset, MFA approval, account access, data release, document sharing, exception approval, visitor access, or process bypass
  • claiming that normal approval, ticketing, verification, procurement, legal, HR, finance, or identity workflow is too slow or unnecessary
  • using “approved by”, “on behalf of”, “required by”, “authorised by”, or “directed by” language without a verifiable record
  • asking the target to act before checking with a manager, approver, legal contact, security team, or process owner
  • treating challenge, clarification, or delay as disobedience or non-compliance

Pressure and manipulation behaviour

  • creating fear of consequences for non-compliance or delay
  • using duty, loyalty, professionalism, compliance, or operational responsibility to pressure action
  • escalating after hesitation, refusal, or requests for verification
  • implying that the target will cause operational, financial, legal, reputational, safety, or disciplinary harm if they do not comply
  • using confidential or sensitive framing to isolate the target from colleagues or second opinions

Timing and context

  • contacting the target during busy, stressful, after-hours, incident, audit, payroll, finance, legal, or operationally sensitive periods
  • applying pressure when normal approvers, managers, or control owners may be unavailable
  • using a plausible deadline that is difficult for the target to verify quickly
  • targeting people in support, finance, HR, legal, reception, executive support, supplier management, identity, or operational roles