Security

Against attackers that move in seconds, I argue only constant monitoring keeps up: the hours nobody is watching, with sources.

• The hours nobody is watching
• The shrinking exploit window
• What attackers are documented doing with AI
• What watching all the time looks like
• The basics still matter · coming
• Defending the agents themselves · coming
• Alert fatigue and the person in the loop · coming

Where a request comes from earns it nothing: be the policy engine, plant an attacker, relay a login.

• The castle and the moat
• Every request is a decision
• Phishing-resistant MFA
• Is this device healthy? · coming
• Context, and why location is only a hint · coming
• Least privilege and microsegmentation · coming
• Sessions that end, and evaluation that never stops · coming
• Machines need identity too · coming
• How mature are you? · coming
• If you run a small business

Hash a real Bitcoin header and get the block’s own ID back; read an Ethereum explorer page knowing what is on the chain.

• Hashes: fingerprints that change completely
• Recompute it yourself: a chain of real headers
• Merkle trees: one root for every transaction · coming
• Proof of work, and why the past is expensive to change · coming
• Keys, signatures and addresses · coming
• Transactions and state on Ethereum · coming
• Gas and the fee market · coming
• Smart contracts: code, calls and events · coming
• Reading an explorer page
• How an explorer is built · coming
• Reading an explorer safely · coming