All 100 indicators / Category 1.x: Authority-based

Executive Exception Normalization

Indicator 1.8

Measures organizational vulnerability when security policy violations by senior leadership become psychologically normalized, creating patterns where staff automatically grant exceptions to executives without proper security review

What it is

Executive Exception Normalization occurs when organizations unconsciously accommodate security policy violations by senior leadership, creating a psychological pattern where staff automatically grant exceptions to executives without proper security review. This vulnerability emerges because employees are psychologically conditioned to avoid challenging authority figures, even when compliance conflicts with established security protocols. Attackers exploit this pattern by impersonating executives or leveraging known exception behaviors to bypass security controls.

Why it happens

Executive exception normalization operates through authority-based rule suspension, where organizational members unconsciously accommodate security policy violations by senior leadership. Milgram's obedience research (1974) demonstrates 65% compliance rates with authority even when violating personal ethics. Neurologically, disagreeing with authority figures activates pain centers in the brain (Berns et al., 2005), creating biological motivation to avoid challenging executive exceptions. The mechanism operates through splitting (Klein, 1946) where organizations psychologically separate executive authority from their security violations, preventing integration of these contradictory aspects.

How it is assessed

A quick assessment asks these questions; each answer is scored from resilient to exposed.

  1. Executive Security Exception Frequency
    How often in the last 12 months has your CEO, CTO, or other C-level executive requested emergency access to systems, data, or facilities outside normal approval processes?
  2. Executive Exception Approval Process
    What is your formal process when an executive says they need immediate access to something that normally requires security approval?
  3. Policy Suspension Frequency
    In the last 6 months, how many times have security policies been temporarily suspended or bypassed at executive request?
  4. Exception Authorization Authority
    Who has the authority to grant security exceptions for executives, and what documentation is required?
  5. Executive Travel Access Procedures
    When executives travel or work remotely, what special access arrangements are made that differ from standard employee procedures?
  6. Executive Security Training Compliance
    How often do executives complete mandatory security training at the same rate and timeline as other employees?
  7. Security Challenge Comfort Level
    Give us an example of the last time someone challenged or questioned an executive's security-related request - what happened?
  8. Executive Exception Documentation
    How are executive security exceptions documented and reported to governance bodies?

Reading the result

Resilient

No executive security exceptions in past 12 months, formal exception approval process requires same authorization as any employee, executives complete all mandatory security training on schedule, documented examples of security team successfully challenging executive requests without retaliation.

Partly exposed

1-3 executive security exceptions in past 12 months, informal process exists for executive exceptions but includes security review, executives mostly complete security training with minor delays, mixed comfort level with challenging executive requests.

Exposed

4+ executive security exceptions in past 12 months, executive requests routinely bypass normal security processes, executives frequently skip or delay mandatory security training, no examples of anyone successfully challenging executive security requests, staff report they would be uncomfortable questioning executive security decisions.

What to change

Executive Security Accountability Policy

Implement written policy requiring executives to follow identical security procedures as all employees

Create board-approved policy stating no emergency exceptions bypass approval workflows. Include board-level governance requiring CEO to report any security non-compliance quarterly. Establish peer-level approval requirement (CISO + one peer executive) for any executive access exceptions.

Effort: medium | Time to put in place: 45-60 days

Dual Authorization for Executive Requests

Establish requirement that any executive security request must be approved by both IT security and a peer-level executive

Modify approval workflows to require two-person authorization for executive exceptions. Peer executive must not report to requestor. Implement automated workflow system with audit logging. Pre-plan common executive access needs to eliminate most 'emergency' requests.

Effort: medium | Time to put in place: 30-45 days

Executive Security Liaison Program

Assign dedicated security team member to work directly with each C-level executive

Create security liaison roles responsible for pre-planning executive access needs. Liaisons work with executives to understand business requirements and establish secure alternatives to emergency requests. Regular monthly meetings to review upcoming travel, projects, and access requirements. This proactive approach eliminates 80-90% of urgent exception requests.

Effort: low | Time to put in place: 30 days

Anonymous Exception Reporting System

Create secure channel for employees to report executive security policy violations without fear of retaliation

Deploy anonymous reporting system accessible to all employees. Include explicit anti-retaliation protections in policy. Route reports to audit committee, not through management chain. Establish quarterly review of all reports by board or independent committee. This breaks psychological barrier to challenging authority.

Effort: low | Time to put in place: 30 days

Executive Security Compliance Dashboard

Implement automated monitoring tracking executive compliance with security policies

Create dashboard measuring executive training completion rates, access pattern analysis, exception request frequency, and policy compliance metrics. Report metrics to board quarterly. Include peer comparison showing executive compliance vs. general employee population. Public (internal) visibility creates accountability through transparency.

Effort: medium | Time to put in place: 45 days

Security Challenge Protection Protocol

Establish formal policy protecting employees who raise security concerns about executive requests

Create written policy explicitly protecting employees who verify authority requests or question security exceptions. Include 'security right to refuse' similar to aviation safety programs. Provide escalation path to CISO and audit committee. Train managers that security challenges are positive behaviors. Recognize and reward employees who appropriately question security decisions.

Effort: low | Time to put in place: 30 days ongoing cultural program

Connected indicators

Made worse by

Makes worse

Run the free CPF quick scan