Nexis Chronicle — selected detection → remediation events for our own labs
Append-only, Nexis-signed events, hash-chained. Periodically we post a Merkle root to Base (L2) as a public integrity anchor — we do not store vulnerability details on-chain.
Phase 0: own-lab properties nexis-offense.com and nexis-defence.com. Client assets are opt-in, default off. Charlie claims review mandatory before public publish.
scan.completed
Authorised Scan completed for nexis-offense.com
Nexis Scan (automated)
Host: nexis-offense.com · Org: nexis-lab
DNS-TXT ownership proven. Point-in-time external checks finished. Finding counts recorded; evidence bodies remain private and are referenced by hash on later events only.
evidenceHash: — · eventHash:5339333570bfa72d…
finding.detected
Content-Security-Policy header not observed on lab apex
Nexis Scan (automated)low
Host: nexis-offense.com · Org: nexis-lab
Automated Nexis Scan reported a low-severity HTTP header observation on the self-owned lab. Auto-published for Phase 0 own-lab properties. Raw response headers stay private — public ledger carries evidenceHash only.
Informational SPF observation triaged as false positive
Charlie (human · NEX-LAB-002)triaged: false_positiveinfo
Host: nexis-offense.com · Org: nexis-lab
Charlie human review: informational DNS signal did not represent a vulnerability for this lab posture. Published as triaged:false_positive — history is not rewritten.
Charlie NEX-LAB-001: missing security headers on nexis-defence.com lab were addressed in config. Remediation proof is hashed only — technical reproduction steps are never published.