Author Archives: Loretta George

You have a file. It came from a website, a release page, a mirror, or an email. Before you run it, you can check one thing: whether the file matches what the publisher signed. That check is called OpenPGP signature … Continue reading →

Your network is talking. Every device that connects to your router asks a domain name server (DNS) to translate a human-readable name like example.com into an IP address. Those requests are a record of what your devices are trying to … Continue reading →

The document you’ll have in your hands by the end of this article is a two-page script. Not a policy. Not a vendor risk assessment. A script — the kind with scene headings, a protagonist who wants something, and decision … Continue reading →

Public accountability in cybersecurity comes down to one thing: security claims that people outside the organization can check. A patch policy, a breach notification, a procurement contract, a management attestation — each counts as accountable when four conditions hold. Somebody … Continue reading →

… … ” } Let me write out the final JSON now.{ “title”: “Why Cybersecurity Needs More Public Accountability: Deadlines, Documents, and Claims You Can Verify”, “html”: “ Public accountability in cybersecurity means security claims that people outside the organization … Continue reading →

Open source software runs on a simple promise: anyone can read the code, so anyone can check what it does. That promise sits at the heart of open security for democratic societies. A supply chain attack flips that promise against … Continue reading →