What the 1988 Morris worm changed for software security
The Morris worm of November 1988 spread through weak passwords and known holes, and it led to the first CERT. Here is what it changed and what it did not.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
The Morris worm of November 1988 spread through weak passwords and known holes, and it led to the first CERT. Here is what it changed and what it did not.
Monte Carlo simulation turns ranges for frequency and cost into a spread of possible losses. See how it works with a small example and its limits.
Model collapse is a documented effect of training on generated data, but it does not mean every AI-written sentence ruins a model. Myths and facts, sorted.
Microsoft's 2016 account of the Tay chatbot: a coordinated attack within 24 hours, the stated lessons, and a launch checklist that still applies.
Self reported speedups can mislead. A method for measuring AI coding impact with baselines, paired metrics and control groups that holds up under scrutiny.
In June 2023 a New York federal judge sanctioned lawyers who filed ChatGPT invented cases. What the order said and the duty it left in place.
What M&S's chairman told Parliament about the April 2025 attack, what stays unconfirmed, and how to harden password reset and outsourced help desk steps.
A checklist for security managers: workload checks, rotation fairness and one to one questions that catch burnout early. Not a medical diagnosis.
Open Source Guides lists signs of maintainer burnout and offers a simple pace test. Here is how to spot it in yourself and in projects you depend on.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.