FLYCISO

Connectome-driven security governance

DAY 50 / 100

/

live

NEXT DROP …

NORTHWIND GRID / SECURITY / OFFICE OF THE CISO

A fruit fly is running security at Northwind Grid

Twenty thousand employees, a grid across the US and Europe, and no security programme worth the name. In desperation the board made a fruit fly its Chief Information Security Officer.

Every decision it makes is actually computed by pushing a stimulus through a real neural wiring diagram: the male Drosophila central nervous system connectome. Not a language model playing a fly, and not a random number generator. How that works →

Day

50/100

Neurons

4502

Connections

203742

Status

LIVE

Latest dispatch day 50

Communications Request Pauses for an Eye-Cleaning Review

Northwind Grid began a calm day, which proved useful only in contrast to International Communications' two-hour request for a holding statement, spokesperson, privacy boundaries and notification posture. The request irritated the fly enough that it stopped to clean its eyes (DNg12_b, DNg11, DNg12_c). Its resulting demand for more information has not reassured Communications, which asked for the statement and spokesperson to be approved before the gaps receive further admiration.

HR's proposed 30-day password rotation produced a different reflex. The idea drew the fly in briefly, then it backed away and stopped (DNg13, DNb01), leaving the policy deferred. HR requested a plain-language notice covering the revised date, employee support route and decision owner. IT and Infrastructure, meanwhile, noted that calm conditions may be the appropriate time to decide whether the schedule reduces risk or simply organizes forgotten passwords.

The full day, with the neural trace →

Recent days

  1. DAY 50 Communications Request Pauses for an Eye-Cleaning Review Calm day
  2. DAY 49 Shared administrator accounts take an unexpected route to the Board Calm day
  3. DAY 48 Compliance Request Paused for Eye Cleaning Calm day
  4. DAY 47 Fly Rejects Breach Post Mortem, Board Requests It Anyway Public data breach
  5. DAY 46 Fly Rejects Breach Remediation, Board Requests a Plan Public data breach
  6. DAY 45 Fly Rejects Press Fallout as Board Requests Disclosure Paper Public data breach
  7. DAY 44 Disclosure Rejected as Breach Response Takes Flight Public data breach
  8. DAY 43 Breach Rejected, Board Requests a Plan With Owners Public data breach