All 100 indicators / Category 10.x: Critical convergent states
Indicator 10.2
Detects psychological conditions where isolated security incidents spread throughout organizations like wildfire through stress contagion, communication breakdown, and decision-making degradation
Cascade failure triggers occur when organizational stress causes isolated security incidents to propagate across departments through psychological contagion. When one person or team becomes overwhelmed during a crisis, their panic, poor decisions, or communication breakdown creates a domino effect that disables security controls across multiple departments. This psychological contagion transforms minor incidents into major breaches because stressed employees bypass procedures, make configuration errors, and fail to coordinate responses effectively.
Emotional Contagion Studies (Hatfield et al., 1994) demonstrate emotions spread automatically through organizations within minutes. Stress Contagion Research (Westman, 2001) shows stress transfers between individuals through multiple mechanisms. Mirror Neuron Systems enable automatic replication of observed stress behaviors. Limbic Resonance (Lewis et al., 2000) shows emotional brain states synchronize between individuals. Bion's Basic Assumptions (1961) reveal groups under stress revert to primitive psychological defenses that cascade through organizational networks.
A quick assessment asks these questions; each answer is scored from resilient to exposed.
Formal incident command structure with defined roles. Communication channels remain functional during stress with backup systems. Security exceptions require documented justification and tracking. Leadership communicates transparently during challenges. Clear business continuity plans address cross-department dependencies. Documented succession planning for security decision-making. Structured alert triage process with defined escalation.
Informal coordination during incidents with some defined processes. Communication strained during stress but doesn't completely break down. Some tracking of security exceptions but approval processes may be bypassed. Leadership communication inconsistent during stress. Some understanding of dependencies but limited contingency plans. Backup decision-makers identified but authority unclear. Alert prioritization exists but may break down under high volume.
No clear incident coordination structure or ad-hoc responses. Communication channels regularly overloaded or bypassed during stress. Security exceptions approved informally without tracking during urgent situations. Leadership unavailable or visibly stressed during challenges. Limited awareness of cross-department dependencies and cascade risks. No clear backup decision-making authority or conflicting authority during crisis. Alert responses become arbitrary or delayed when team overwhelmed.
Implement mandatory labeling system for all AI-generated communications
Deploy technical controls that automatically tag AI messages with clear identifiers. Establish verification requirements for any unlabeled communications claiming human origin. Create escalation pathway for communications that lack proper AI/human identification.
Develop 20-minute training module teaching employees to recognize and trust their 'uncanny' feelings
Include practical exercises using examples of legitimate vs malicious AI communications. Train employees to use verification protocols when experiencing psychological discomfort with digital interactions. Provide clear scripts for escalating 'something feels wrong' concerns to security teams.
Establish policy requiring verification through separate communication channel for any high-stakes requests
Implement technical system that automatically prompts verification for financial, access, or sensitive data requests. Create simple process for employees to quickly verify human identity through alternative means. Deploy phone or in-person verification requirements for unusual requests, regardless of source authenticity.
Create formal process for employees to report 'uncanny' or uncomfortable digital interactions without judgment
Establish security team response procedure for investigating ambiguous AI-human communications. Implement policy protecting employees who escalate based on intuitive concerns rather than technical evidence. Deploy rapid-response system for employees experiencing confusion about communication authenticity.
Deploy system to monitor patterns in employee responses to AI communications
Establish baseline metrics for normal AI interaction behaviors (response times, verification requests, escalations). Create alerts for unusual patterns that might indicate uncanny valley exploitation. Implement automated detection for communication patterns that typically trigger uncanny valley responses.
Deploy multi-factor verification system triggered by employee uncertainty reports
Implement biometric or behavioral authentication for video/audio communications when requested. Create technical controls that flag communications exhibiting uncanny valley characteristics. Establish secure verification codes or phrases for confirming human identity in suspicious interactions.