All 100 indicators / Category 10.x: Critical convergent states

Emergence Unpredictability

Indicator 10.8

Detects organizational failure to comprehend how complex systems produce unexpected security failures through interaction of seemingly unrelated components

What it is

Emergence unpredictability represents a psychological vulnerability where individuals and organizations fail to recognize that complex systems can produce emergent behaviors that cannot be predicted from understanding individual components. This stems from fundamental cognitive limitations including linearity bias, reductionist thinking, and illusion of control when confronted with complex, interconnected systems.

Why it happens

Systems Theory (Bertalanffy, 1968) - complex systems exhibit emergent properties unpredictable from components alone. Complexity Science (Holland, 1995) - adaptive systems produce emergent behaviors through non-linear interactions. Prospect Theory (Kahneman & Tversky, 1979) - humans systematically misjudge probabilities for novel scenarios. Neuroscience (Bar, 2007) - brain's predictive coding fails when encountering truly emergent phenomena.

How it is assessed

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

  1. Question Title
    How often does your organization conduct security assessments that specifically examine interactions between different systems (IT, physical security, HR processes, third-party services)?
  2. Question Title
    When you experience a security incident, what's your standard procedure for analyzing root causes?
  3. Question Title
    How frequently do you test scenarios where multiple, seemingly unrelated changes happen simultaneously (software updates + staff changes + vendor modifications)?
  4. Question Title
    What's your process when security monitoring alerts don't match any known attack patterns?
  5. Question Title
    How do you assess security risks when implementing new technology that will interact with existing systems?
  6. Question Title
    What's your procedure for identifying potential security implications when non-IT departments make operational changes?
  7. Question Title
    How often do you conduct 'red team' exercises that explore novel attack combinations rather than testing known vulnerabilities?

Reading the result

Resilient

Quarterly cross-system security reviews conducted. Formal procedures for multi-factor incident analysis. Regular testing of novel threat combinations. Cross-departmental security change protocols maintained. Dedicated resources for emergence scenario planning. Rewards for identifying novel risk combinations.

Partly exposed

Some cross-system awareness but reviews annual or less frequent. Incident analysis sometimes considers system interactions. Occasional testing of combined scenarios. Informal coordination between departments on security implications. Limited emergence scenario planning. Focus primarily on known threat patterns.

Exposed

Focus on individual system security with minimal cross-system analysis. Incident response targets single root causes. Rarely tests novel threat combinations. Departments operate in silos regarding security changes. Treats security risks as predictable and controllable. Linear thinking dominates security planning.

What to change

AI Communication Labeling Protocol

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.

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

Uncanny Valley Response Training

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.

Effort: low | Time to put in place: 30 days initial, quarterly updates

Two-Channel Verification System

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.

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

Psychological Safety Protocols

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.

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

AI Interaction Baseline Monitoring

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.

Effort: high | Time to put in place: 60-90 days

Enhanced Authentication for Ambiguous Communications

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.

Effort: high | Time to put in place: 60-90 days

Run the free CPF quick scan