1975 Sep
Saltzer and Schroeder publish eight protection principles
The paper organized recurring protection choices into eight design principles, including fail-safe defaults, complete mediation, open design, and least privilege.
Security
How the field of a Security Engineer got here: the sourced milestones from every published course of this career, on one axis.
1975 to 2025
490 milestones across 51 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
20 milestones
1975 Sep
The paper organized recurring protection choices into eight design principles, including fail-safe defaults, complete mediation, open design, and least privilege.
1976 Nov
The paper introduced public-key distribution and digital-signature concepts. It established the cryptographic foundation that PKI later governs at scale.
1977 Jan 15
The U.S. standard specified a shared-key encryption algorithm for protecting sensitive computer data and placed implementation in electronic devices.
1978 Feb
Rivest, Shamir, and Adleman published a practical public-key encryption and signature method. RSA became one of the algorithms used with public-key certificates.
1980
The OECD issued privacy principles for personal-data protection and transborder data flows. The principles gave later engineering and regulatory work a shared vocabulary for collection, use, safeguards, openness, participation, and accountability.
1980 Apr
James P. Anderson's report described using audit information to distinguish normal use from suspected misuse. It established audit review as a basis for automated intrusion detection research.
1982 Apr 14
The standard defined general security requirements for equipment that implemented DES, extending attention from the algorithm to its operating boundary.
1982 Aug
SMTP standardized interoperable mail transfer and relay. Its store-and-forward design created the cross-domain trust boundary that later email-security controls protect.
1983
Cohen's controlled experiments and later publication formalized computer viruses as a subject for technical study rather than only an operational incident.
1984
The foundational patent for challenge-response authentication using public-key cryptography, which later underpinned hardware token systems for decades.
1985 Aug
Dorothy Denning and Peter Neumann documented requirements for a real-time Intrusion-Detection Expert System. The work connected statistical profiles and expert-system rules to system audit records.
1985 Dec
The final Trusted Computer System Evaluation Criteria connected security features with assurance requirements and defined graded evaluation classes for computer systems.
1986
The first widely deployed hardware OTP token, generating codes from a time-synchronized algorithm. SecurID became the enterprise standard for second-factor authentication for over two decades.
1987
The Act assigned NBS, later NIST, responsibility for computer security standards for unclassified federal systems. It established a durable public role for program guidance and training.
1987 Feb
The model described detecting security violations through abnormal patterns in audit records. It gave the field a general framework independent of a particular system or vulnerability.
1988 Nov
The Morris Worm disrupted the early Internet on November 2, 1988. DARPA asked the Software Engineering Institute to establish the coordination center that became CERT/CC so incident analysis and communication could be coordinated.
1988 Nov
CCITT X.509 specified public-key certificates, certification authorities, and strong authentication within the Directory. It supplied the certificate model used by later Internet profiles.
1988 Nov 2
The Morris Worm disrupted the early Internet. DARPA asked the Software Engineering Institute to establish the CERT Coordination Center to coordinate vulnerability reporting and incident response.
1988 Nov 25
ITU approved X.500 as an overview of directory concepts, models, and services. Directory standards gave distributed identity records a common information and service model.
1989
The first ransomware attack used infected diskettes and a ransom demand after repeated system reboots. It established the extortion pattern before modern internet-scale delivery.
42 milestones
1990
The Forum of Incident Response and Security Teams formed after separate response teams encountered coordination problems across constituencies, languages, and time zones. Security response gained a continuing international coordination forum.
1991
EICAR created a vendor-neutral forum for anti-malware research and later distributed a non-malicious test file for safely checking antivirus response.
1991
PGP made public-key cryptography and signatures broadly available in software. Its message and key concepts became the basis for the later OpenPGP format.
1991 Jun 13
Digital Equipment Corporation delivered the SEAL firewall, combining a packet-filtering gateway with application proxy and mail components. It became an early commercial firewall architecture.
1992 Apr
The AICPA issued Statement on Auditing Standards No. 70 for reporting on controls at service organizations, which became the dominant US mechanism for those examinations for nearly two decades.
1992 Oct
Ferraiolo and Kuhn presented a formal role-based access control model in which access is mediated through roles. The model generalized earlier application-specific role controls.
1993 Feb
RFC 1422 specified a certificate-based approach to key management for Internet privacy-enhanced mail. It showed an early Internet use of X.509 certificates and defined validity intervals as an operational concern.
1993 Feb
Privacy Enhanced Mail used X.509 certificates and a hierarchical policy structure for Internet email. The document is now Historic, but it records an early Internet PKI design.
1993 Jul
The IETF published a lightweight client-server protocol for accessing X.500 directories. It reduced dependence on heavier directory access mechanisms.
1993 Jul
The first LDAP RFC defined a lightweight access protocol for clients that could not carry the full X.500 Directory Access Protocol stack.
1993 Sep
The IETF specification documented ticket-based authentication across network services. Managed environments could reuse a central authentication relationship without sending a password to every service.
1994
Canada, France, Germany, the Netherlands, the United Kingdom, and the United States unified earlier evaluation criteria. This created shared vocabulary for evaluating security properties across markets.
1994 Jan 11
FIPS 140-1 set security requirements for cryptographic modules across interfaces, roles, physical security, software, key management, and self-tests.
1994 Nov
The result established a polynomial-time quantum attack on the mathematical problems underlying major public-key systems.
1994 Dec
NIST documented firewall components, access policies, and implementation choices to help organizations plan and purchase Internet firewalls.
1995
Vern Paxson designed and implemented the initial Bro network monitor. Its event-oriented analysis later continued under the Zeek name.
1995
The PKIX working group began work on Internet standards for X.509-based public key infrastructures. Its charter connected certificate formats to interoperable Internet deployment and validation practice.
1995
PKI standards work shifted toward the IETF, and the PKIX group developed Internet profiles for X.509. This work connected the general X.509 framework to interoperable Internet use.
1995 Feb
Netscape released SSL 2.0 as the first public transport encryption protocol for the web. Its design limitations—MD5-only MAC, shared encryption and authentication key, unprotected handshake—drove a complete redesign within a year.
1995 Mar
The revised protocol replaced RFC 1487 and documented the bind, search, modify, add, delete, Modify RDN, compare, abandon, and unbind operations.
1995 Oct
Directive 95/46/EC established a European legal framework for personal-data processing. It made system processing practices a sustained regulatory concern rather than a policy-only topic.
1995 Oct
The handbook organized information security policy, program management, and control concepts into public federal guidance. It gave practitioners a durable vocabulary for connecting management direction to safeguards.
1995 Oct
The original Introduction to Computer Security organized foundational security principles and management concerns for organizations.
1996 Jul
The algorithm established a quadratic speedup for unstructured search, shaping how symmetric key sizes are assessed under a quantum threat model.
1996 Nov
A complete protocol redesign by Kocher, Karlton, and Freier separated data transport from the message layer and added Diffie-Hellman key exchange. SSL 3.0 became the foundation for all subsequent TLS versions.
1997 Sep
The Site Security Handbook described filtering, proxy services, and firewall architecture as parts of Internet-connected site security.
1997 Dec
LDAPv3 added an extensible message structure and became the protocol generation on which current LDAP specifications are based.
1998
Martin Roesch released the software that became Snort as an open network sniffer. The project provided a foundation for widely deployable rule-driven inspection.
1998 Mar
S/MIME described cryptographic message content protection for MIME mail. It established a message-level alternative to protecting only the transport connection.
1998 Aug
The OpenLDAP Project published its first release, establishing an open implementation with server, client, and library components.
1998 Nov
RFC 2401 defined a security architecture for IP traffic using authentication, encapsulation, and security associations. It gave site-to-site and host-to-host protection a common standards-track foundation.
1998 Nov
RFC 2440 standardized OpenPGP message formats, signatures, keys, and certificates. Software signing could then use an interoperable public-key format rather than a single implementation's convention.
1999
International standardization extended the common evaluation criteria beyond the original government collaboration. Product assurance and configuration claims gained a common international reference.
1999
Intrusion detection capability changed Snort from a sniffer into a network IDS. Practitioners could express and share traffic signatures in an open engine.
1999
Loren Kohnfelder and Praerit Garg's internal paper introduced STRIDE. The taxonomy gave software teams a repeatable way to enumerate threats during design analysis.
1999 Jan
The PKIX profile standardized certificate and revocation-list use for Internet applications. Later revisions refined the validation model and profiles.
1999 Jan
RFC 2459 profiled X.509 certificates and certificate revocation lists for Internet use. It made extensions and certification-path processing central parts of interoperable certificate handling.
1999 Jan
The IETF standardized SSL as Transport Layer Security. TLS 1.0 replaced the custom MAC with HMAC and expanded alert codes, but remained close enough to SSL 3.0 that downgrade attacks were a known concern from the start.
1999 Jun
RFC 2616 standardized HTTP/1.1. Its method, header, and response model became a common transport surface for web APIs and their security controls.
1999 Aug
RFC 2647 defined common terms for packet filtering, stateful filtering, proxies, rulesets, and protected networks so implementations could be discussed and benchmarked consistently.
1999 Sep
The CVE Program launched its public list with a common set of identifiers for known vulnerabilities. Security teams and products gained a shared reference for exchanging vulnerability information.
1999 Sep
RFC 2696 defined a control and opaque cookie exchange for retrieving a large search result in pages.
109 milestones
2000
Active Directory Domain Services first became available with Windows 2000. It established the domain-controller directory that later security controls protect.
2000
Shibboleth grew from an Internet2 middleware initiative and connected with the OASIS SAML work. It established an open federation path for research and education institutions.
2000 May
RFC 2830 defined the extended operation that begins TLS on an LDAP association, providing confidentiality, integrity, and optional authentication.
2000 Oct
The RFC documented interoperability requirements and showed how filtering could disrupt Path MTU Discovery and application protocol negotiation.
2001
Vontu launched in San Francisco to detect and block disclosure of sensitive data by policy. Its product was later described as the first to combine endpoint and network coverage for data at rest, in motion, and in use, the three-state framing DLP still uses.
2001 May 25
FIPS 140-2 replaced FIPS 140-1 and retained four qualitative security levels while updating the areas used to assess cryptographic modules.
2001 Jun
NIST SP 800-27 moved system-level principles into federal guidance for the design, development, and operation of information systems.
2001 Aug
RFC 3164 documented the widely implemented BSD syslog message and relay model. It gave centralized collectors a shared reference while also recording delivery and security limitations.
2001 Sep
OWASP began as an informal open community. It became a home for shared application-security projects and practitioner guidance.
2001 Nov
NIST published an enterprise primer on selecting, configuring, managing, and integrating intrusion detection systems. It formalized IDS as part of organizational security infrastructure.
2001 Nov 26
FIPS 197 standardized AES with 128-bit blocks and three supported key sizes, creating the symmetric cipher foundation used by later key hierarchies.
2001 Dec
OWASP launched as an open community focused on improving software security. Its projects made application-security guidance broadly accessible to development teams.
2001 Dec 1
OpenBSD introduced PF as its packet filter with network address translation. The project later documented filtering, tables, logging, traffic control, and redundancy around the same system.
2002
Development began to address high concurrent-connection workloads with an event-driven architecture. That origin explains why NGINX became a common edge component whose listeners and request-processing path need explicit protection.
2002
NIST SP 800-43 provided system administration guidance and configuration checklists for Windows 2000 Professional. It was an early step toward reusable product-specific secure configuration guidance.
2002
The first Developer Guide established an early developer-facing reference for secure development practice.
2002
Microsoft's Trustworthy Computing directive led product groups to run security pushes that included threat modeling and mitigation. It moved the practice toward a development-process expectation.
2002 Jan
Microsoft started Trustworthy Computing in response to the changing security environment. The initiative made security a development concern instead of a late product concern.
2002 Jan
NIST issued dedicated guidance on firewall technologies and policy, turning deployment and management into a documented security lifecycle.
2002 Apr
RFC 3280 replaced RFC 2459 as the Internet X.509 certificate and CRL profile. It carried the profile forward for certificate construction and path validation.
2002 Sep
The technical specification assembled the RFC set required for an LDAPv3 implementation and clarified the standards baseline.
2002 Nov
NIST SP 800-48 set out security recommendations for wireless networks as WLAN use expanded. It established that radio networks needed dedicated configuration, access-control, and monitoring treatment.
2002 Nov
OASIS ratified the first SAML standard, establishing an XML framework for exchanging authentication and authorization information.
2002 Nov 1
OASIS approved an XML framework for authentication, attribute, and authorization assertions. It established an interoperable foundation for browser single sign-on across security domains.
2002 Dec
FISMA tasked NIST with federal standards and guidelines and required documented agency-wide information security programs.
2003
The Windows Server 2003 functional level added constrained delegation. Delegation became a configuration surface requiring explicit security review rather than a purely application concern.
2003
The first OWASP Top 10 gave developers and organizations a common awareness document for major web application risks.
2003
The first Shibboleth identity-provider release made SAML federation deployable in research and education communities. Institutions could operate their own IdPs and exchange attributes with participating services.
2003 Aug
NIST published its initial guide for using performance measures to assess information security controls, policies, and procedures.
2003 Sep
Version 1.1 incorporated implementation experience and refined the assertion, protocol, binding, and profile set.
2003 Nov
The framework organized the topics covered by certificate policies and certification practice statements. Operators gained a common structure for documenting governance and operational controls.
2004
Microsoft made its Security Development Lifecycle part of its software development process, integrating security work across design, development, and testing.
2004
Microsoft made its Security Development Lifecycle a mandatory policy. Secure development became an organizational process with required activities rather than guidance teams could choose to skip.
2004
The Security Development Lifecycle became integral to Microsoft's development process. Threat modeling was established as a design-phase activity alongside security testing and review.
2004
RSA hardware token install base demonstrates the market for something-you-have authentication, though cost and logistics keep it confined to regulated and enterprise environments.
2004
Inline capability allowed Snort to stop malicious traffic instead of only reporting it. The operational concern expanded from detection accuracy to traffic-path availability and false-block impact.
2004
Microsoft released Windows Firewall as a component of Windows XP Service Pack 2, moving host-based filtering into a widely deployed operating system baseline.
2004 Feb 11
The NIST RBAC model became an American National Standard. This gave role, permission, hierarchy, and constraint concepts a common standard form.
2004 Jun
Revision A clarified a structured foundation that covered technical countermeasures alongside policy, procedures, and user education.
2004 Jun 1
VirusTotal made aggregated scanner results and shared sample context available through an online service, changing reputation lookup and collaborative triage.
2004 Jul
The Jericho Forum argued that a hard trusted-inside boundary could not support open collaboration. Its presentation shifted protection toward data, systems, interoperable controls, and defense in depth.
2004 Oct 4
NGINX 0.1.0 became publicly available. Operators could begin deploying the software as a web server and proxy, making configuration and exposed modules operational security concerns.
2004 Dec
The Testing Guide established a documented approach to web application security testing, separate from implementation guidance.
2005
FastCGI support and a common upstream module expanded the ways NGINX could sit in front of application services. Hardening therefore had to consider both client-facing and upstream boundaries.
2005
ISO published the first ISO/IEC 27001 edition, establishing an information security management system standard. It made risk-based management and continual improvement a formal management-system path for information security.
2005
Microsoft's public SDL material described threat modeling and testing as part of a repeatable secure-development process. The practice became accessible beyond its original internal use.
2005
MITRE grouped real CVE examples into common fault and flaw classes. The work supplied a bottom-up basis for a shared weakness taxonomy.
2005 Feb
NIST published a catalog for selecting and specifying security controls for federal information systems. It established a repeatable control selection approach that accounts for system categorization.
2005 Mar
OASIS approved SAML 2.0 and unified federation building blocks from SAML, Shibboleth, and the Liberty Alliance. Its assertions, bindings, profiles, and metadata remain a common enterprise SSO integration boundary.
2005 Mar
Version 2.0 unified prior SAML work with federation capabilities contributed from the Liberty Alliance identity-federation framework.
2005 Mar
OASIS published SAML 2.0, defining the assertion, binding, profile, and metadata vocabulary that underpins many enterprise browser SSO integrations.
2005 May
NIST SP 800-70 defined guidance for checklist users and developers while a public repository opened with more than one hundred checklists. Secure configuration guidance became easier to discover and reuse.
2005 Aug
The first final Part 1 assembled general guidance for cryptographic key types, protection, lifecycle, cryptoperiods, compromise, and recovery.
2005 Oct
ISO and IEC published ISO/IEC 27001:2005 for information security management systems. The standard tied risk-based management to the selection of proportionate controls for information assets.
2005 Oct
The first edition specified requirements for a documented information security management system in the context of organizational risk. It made the management system itself a certifiable requirements structure.
2005 Dec
The HMAC-Based One-Time Password algorithm standardizes event-driven OTP generation, giving the industry an open alternative to proprietary token systems and enabling interoperable hardware and software authenticators.
2006
The idea arose at the C Standards Committee meeting in Berlin. The project targeted actionable security guidance for C programmers.
2006
The first Common Weakness Enumeration list established community definitions and classifications for recurring software weaknesses.
2006
SCAP began as a program to standardize machine-readable security configuration and vulnerability information. This moved configuration assessment toward interoperable automation.
2006
NIST published Information Security Handbook: A Guide for Managers. It connected information-security program governance with management roles, controls, and performance measures.
2006
Microsoft records 2006 through 2008 as the period when the SDL was released publicly and threat-modeling tooling collaboration expanded. This positioned design analysis as a reusable industry practice.
2006 Apr
Domain owners gained a standardized way to identify hosts authorized to send mail for an envelope domain. This added a delivery-layer check against some spoofed mail.
2006 Apr
SPF documented DNS-published authorization of SMTP senders. It made the envelope sender identity an operational authorization target.
2006 Apr
Added explicit per-record initialization vectors for CBC cipher suites, addressing the chosen-plaintext weakness that the BEAST attack later demonstrated against TLS 1.0 in practice.
2006 May
Upstream blocks made backend groups a first-class configuration concept. Proxy policy now needed to include backend selection, timeout behavior, and later TLS peer verification.
2006 Jun
The revised document set separated the protocol, information models, security, names, filters, URLs, syntaxes, matching, and user schema.
2006 Aug 24
Self-service compute became available to anyone with a credit card, minutes after signup. The operating split between a provider that runs the hardware and a customer that runs everything above it arrived before any shared framework described who owned which control.
2006 Sep
NIST SP 800-92 described log-management infrastructure, planning, and operational processes across an enterprise. Logging became an explicit program that supported analysis and incident handling rather than a collection of isolated files.
2006 Sep
NIST published enterprise guidance for computer security log management. The guide described centralized infrastructures and identified SIEM as a class of analysis-focused logging software.
2006 Oct
The handbook assembled program elements for managers establishing and implementing an information security program.
2006 Dec
NIST published a revised security-control catalog for federal information systems. It gave access-control and account-management practices a common control baseline.
2007
NIST issued the final update to SP 800-100. Its handbook framing kept governance and management distinct from operational security work.
2007 Feb
NIST replaced its IDS guide with guidance covering detection and prevention. It organized enterprise technology into network-based, wireless, network behavior analysis, and host-based classes.
2007 May
DKIM standardized domain-associated message signatures. Receivers could validate a signing domain independently of the SMTP path.
2007 May
DKIM standardized domain signatures over email content so receivers could verify responsibility for a message. The specification identified phishing control as one intended benefit.
2007 May
The commandments documented design principles for systems operating beyond a fixed perimeter. They connected open networks with data protection, identity, trust, and policy enforcement.
2007 Aug
The open framework made repeatable extraction of processes, mappings, and other artifacts from volatile memory available to investigators and malware analysts.
2007 Nov
OASIS approved metadata extensions for standalone query requesters and a profile for describing SAML 1.x entities with SAML 2.0 metadata.
2007 Nov
Symantec announced the purchase of Vontu for 350 million dollars and completed it at the end of the month. The deal moved DLP from a niche category into the portfolios of mainstream enterprise security vendors.
2007 Dec
Revision 2 updated the control catalog. Organizations could continue to map account, privilege, and separation-of-duties practices to a maintained baseline.
2008
Windows Server 2008 introduced fine-grained password and account-lockout policies. Administrators could apply different password controls to users and groups within one domain.
2008
Microsoft published its Security Development Lifecycle approach for security and privacy considerations across development phases. The approach became a public reference for formal lifecycle practice.
2008
Microsoft moved its internal lifecycle practices into publicly available guidance and tools for wider secure-development adoption.
2008 Mar
New profiles specified attribute exchange and SAML subject representation for systems that authenticate principals with X.509 certificates.
2008 Apr
The ASVS proposal entered OWASP Summer of Code, beginning work on a set of verifiable application security requirements.
2008 May
The Time-Based One-Time Password standard builds on HOTP with a time source, enabling the authenticator apps and software tokens that make MFA accessible beyond organizations that can issue hardware.
2008 May
RFC 5280 obsoleted earlier PKIX profiles and specified X.509 version three certificate, CRL, and path-validation processing for Internet use.
2008 May
RFC 5280 replaced RFC 3280 and specified the certificate and CRL profile used for Internet PKI path validation. Its extension and constraint rules remain a reference for certificate-chain handling.
2008 Jul
NIST SP 800-123 organized server hardening around selecting, implementing, and maintaining security controls. The guidance framed secure configuration as lifecycle work rather than initial setup alone.
2008 Jul
Revision 1 updated performance-measurement guidance and linked measures to resource allocation and reporting.
2008 Aug
McAfee closed its 46 million dollar acquisition of Reconnex, a network DLP and data-at-rest discovery vendor, and folded the technology into ePolicy Orchestrator. Consolidation ran in parallel, with EMC buying Tablus and Websense buying PortAuthority.
2008 Aug
Replaced hardcoded hash functions with cipher-suite-specified pseudo-random functions and added AEAD modes such as AES-GCM. TLS 1.2 remains the compatibility floor for current deployment guidance.
2008 Sep
The guide expanded the testing reference used to assess web application behavior and controls.
2008 Oct
SEI published the first official CERT C Secure Coding Standard, with rules, insecure examples, and secure alternatives for recurring C coding errors.
2009
Active Directory Recycle Bin made deleted objects recoverable without restoring a backup or restarting directory services. It improved object recovery but did not replace forest recovery after compromise.
2009
The CSA incorporated and released Security Guidance for Critical Areas of Focus in Cloud Computing, the first broad attempt to name the customer-side controls that a provider contract does not cover.
2009
The first devopsdays conference brought software development and operations together as one technical conversation.
2009
Ontario's Privacy by Design framework set out seven foundational principles, including proactive design and privacy as the default setting. It helped frame privacy as something built into systems and business practices.
2009
Microsoft's SDL timeline records collaboration with SAFECode, Adobe, Cisco, DISA, and NIST from 2009 through 2011. Threat modeling became part of wider secure-development guidance and exchange.
2009 Mar
OpenSAMM 1.0 introduced an open maturity model for software assurance. Teams could assess and improve capabilities across the software lifecycle instead of adopting one fixed process.
2009 Mar
OpenSAMM introduced a maturity-model approach to software assurance and capability assessment.
2009 Mar
RFC 5424 replaced RFC 3164 with a standards-track, transport-independent protocol and structured data model. It made event format, timestamps, extensions, and transport mappings more explicit.
2009 Apr
NIST published research directions that treated security measurement as a continuing technical and organizational problem.
2009 Aug
The profile defined rules for metadata producers and consumers to provision federation relationships consistently and derive trust processing from metadata.
2009 Aug
Revision 3 delivered a major update to security controls for federal systems and organizations. Its catalog supported consistent requirements while remaining complementary to other standards.
2009 Aug
Revision 3 extended the catalog to federal information systems and organizations. Identity governance could be framed as organization-wide control work rather than a single application setting.
2009 Sep
NIST SP 800-41 Rev. 1 updated its firewall guidance with policy, selection, configuration, testing, deployment, and management considerations. Firewall operation became a lifecycle concern rather than only a perimeter-device purchase.
2009 Sep 28
The revision expanded guidance across network and host-based firewall technologies, placement, policy, testing, deployment, and management.
2009 Nov
NIST SP 800-126 defined the first SCAP version as a suite of specifications for standardized security-software communication. Assessment products could exchange configuration and vulnerability information in defined formats.
182 milestones
2010
The first control framework written specifically for cloud services, mapping each control to the party responsible for it and to existing standards. It made the shared-responsibility split auditable rather than rhetorical.
2010
Cuckoo established an open architecture for launching samples in isolated guests and collecting process, file, memory, screenshot, and network evidence.
2010
The 2010 release framed application security as a people, process, and technology problem, not only a list of code flaws.
2010 Feb
SP 800-37 Revision 1 described a six-step lifecycle with control selection, assessment, authorization, and ongoing monitoring.
2010 Mar
The Open Information Security Foundation launched alongside the first Suricata release. Practitioners gained another open engine designed for network detection, prevention, and monitoring.
2010 Apr
RFC 5849 published OAuth 1.0. It documented a signed-request approach to delegated access before OAuth 2.0 replaced it.
2010 Apr
The AICPA moved service-organization reporting from an auditing standard (SAS 70) to an attestation standard (SSAE 16), aligning more closely with international assurance practice.
2010 May
NIST updated federal contingency planning guidance with risk management and system development life cycle considerations. This reinforced that recovery requires planning for systems and operations, not only backups.
2010 Jun
The assessment guide described procedures for evaluating security controls. This strengthened the distinction between recording an access decision and obtaining evidence that a control operates.
2010 Jul
The root-zone deployment made cryptographic trust anchors available from the top of the DNS hierarchy. It made authenticated DNS responses a practical part of the internet's security architecture.
2010 Jul
NIST SP 800-117 explained how organizations and vendors could use SCAP-enabled tools. The publication connected the specification to baseline verification, monitoring, and security measurement.
2010 Aug
John Kindervag's webinar named a zero-trust model that treated all users as untrusted and placed security throughout the network rather than only at its edge.
2010 Oct 1
KMIP defined a common client-server protocol and profiles for managing cryptographic objects across products that had used incompatible interfaces.
2010 Nov
The profiles standardized ways to express authentication assurance information and an IdP's assurance certification in metadata.
2011
The paper presented intrusion analysis as a sequence of adversary actions and defense opportunities. It gave defenders a behavior-oriented way to organize investigation before the modern hunting vocabulary was common.
2011 Feb 5
The public beta made the automated sandbox available for local deployment and integration into broader analysis systems.
2011 Apr 12
NGINX 1.0 established the first stable release line. Version tracking and advisory review became a clearer operational control for deployed installations.
2011 May
Every AWS account gains an integrated service for creating users, groups, and JSON-based identity-based and resource-based policies, replacing the previous model where every API call used root credentials.
2011 Jun 15
SSAE 16 became required for service organization reports with periods ending on or after June 15, 2011, ending SAS 70 as the governing standard for new reporting periods.
2011 Sep
Rizzo and Duong showed a practical chosen-plaintext attack against TLS 1.0 CBC mode that could recover HTTPS session cookies. The attack validated the per-record IV fix in TLS 1.1 and accelerated the case for TLS 1.2 adoption.
2011 Sep
NIST SP 800-137 defined an organization-wide strategy for ongoing visibility into assets, threats, vulnerabilities, and control effectiveness. Monitoring outputs were tied directly to risk decisions and risk tolerance.
2011 Sep
The guide connected ongoing visibility into assets, threats, vulnerabilities, and control effectiveness with organizational risk tolerance.
2011 Nov
Users and services in one AWS account can assume a role in another account through sts:AssumeRole, enabling delegated administration and the multi-account patterns that underpin modern landing zones.
2011 Dec
ISO/IEC 29100 provided a privacy framework and privacy principles for personally identifiable information processing. It supplied a standards-oriented reference for integrating privacy into information and communication technology systems.
2011 Dec
Government guidance set out the governance, compliance, trust, architecture, identity, data-protection, and incident-response questions an organization has to answer before moving data or workloads to a public cloud.
2012
Windows Server 2012 added a graphical interface for enabling, locating, and restoring deleted objects. Recovery operations became more accessible while retaining the same underlying directory controls.
2012 Jan
NIST described attribute-based access control and the attributes used in policy decisions. This made authoritative identity attributes a more explicit input to access decisions.
2012 Feb
NIST SP 800-153 consolidated recommendations for securing wireless clients, access points, switches, and monitoring throughout the WLAN lifecycle. Wireless security became an operational design and monitoring concern, not only a passphrase choice.
2012 Feb 11
The proposal standardized deriving a full tree of keys from one seed, replacing the practice of generating and separately backing up an independent key for every address.
2012 Mar
The FTC's final report made privacy by design, simplified choice, and greater transparency central recommendations. It connected privacy expectations to product development and data practices.
2012 Aug
NIST revised its Computer Security Incident Handling Guide to address evolving threats and incident response competencies. The guide linked preparation, detection, analysis, containment, recovery, and lessons learned into incident handling practice.
2012 Sep
The Security, Trust, Assurance and Risk registry let providers publish their control self-assessments in a common format, so customers could compare provider claims instead of taking each vendor's word separately.
2012 Oct
RFC 6749 standardized OAuth 2.0 authorization grants and access tokens. API security practice gained a common framework for delegated authorization.
2012 Oct
The IETF standardized an authorization framework for clients to obtain limited access to HTTP services. Its roles and flows later became the base for OpenID Connect authentication.
2013
Microsoft added DLP policy templates, transport-rule conditions, and policy tips to Exchange Server 2013. Content inspection for email moved into the mail server itself rather than a separate appliance or gateway.
2013
The FBI began tracking a financial fraud pattern that combined social engineering, spoofing, compromised communications, and payment authority. Defense practice increasingly had to verify business transactions, not only inspect message appearance.
2013
MITRE began ATT&CK to document adversary tactics, techniques, and procedures for research on endpoint telemetry and post-compromise analytics. Security operations teams gained a shared behavior model for detection and assessment.
2013
NGINX Plus added a commercial product path focused on traffic management, dynamic configuration, and monitoring. Deployments now needed to inventory the edition and its exposed management capabilities as well as the core server configuration.
2013
Protected Users added nonconfigurable restrictions on NTLM, weak Kerberos encryption, delegation, and ticket renewal for its members. It made credential-hardening compatibility a deployment concern.
2013 Feb
The order directed development of a voluntary, risk-based framework for critical infrastructure cybersecurity. It created the policy origin for the NIST Cybersecurity Framework.
2013 Feb
A consortium including PayPal, Lenovo, and Nok Nok Labs forms to develop open authentication standards. The alliance later adds Apple, Google, and Microsoft, and its specifications become the foundation for phishing-resistant MFA.
2013 Apr
Revision 4 integrated privacy controls with security controls. Governance programs could relate identity and access evidence to a broader security and privacy control catalog.
2013 Jun
RFC 6960 updated the Online Certificate Status Protocol. It defined signed status responses for certificate serial numbers, reinforcing that revocation status is evaluated by relying parties under local policy.
2013 Jun
The experimental RFC defined public logs and cryptographic proofs for observing TLS certificate issuance. Domain owners and clients gained a mechanism for detecting publicly logged certificates.
2013 Aug
The updated HTTP profile added Holder of Key subject confirmation and channel-binding support for capable clients that contact identity providers directly.
2013 Sep
CryptoLocker paired malware distribution with encryption and a payment workflow. The Canadian Centre for Cyber Security identifies it as the first modern ransomware campaign.
2013 Sep 10
The proposal standardized converting wallet entropy into a checksummed, human-readable word sequence, turning the single backup an HD wallet needs into something a person can write down and read back correctly.
2013 Nov 13
Account-level recording of API calls became a standard cloud capability. Every administrative change now left an entry naming the identity, the action, the source address, and the result, which is the evidence an investigation depends on.
2014
The CryptoLocker model spread through malicious attachments and broad campaigns from 2014 through 2016. Defense therefore needed to cover access paths and endpoints at scale.
2014
CWE expanded its weakness classifications with content for mobile applications as software platforms and attack surfaces changed.
2014
Google described removing the privileged intranet and making access depend on users and devices. The paper supplied a production example of resource access without location-based trust.
2014 Jan 19
The Linux kernel added nftables as the successor to iptables, using a flexible ruleset representation and a new userspace interface.
2014 Feb
The framework gave organizations a common risk-based structure around Identify, Protect, Detect, Respond, and Recover rather than prescribing one control implementation.
2014 Feb
CSF 1.0 introduced a common outcome structure, including the Core, Tiers, and Profiles, for communicating cybersecurity priorities.
2014 Feb
The first Cybersecurity Framework provided voluntary, risk-based guidance for managing critical-infrastructure cybersecurity. It gave network controls a shared way to connect technical work to organizational risk outcomes.
2014 Feb
The OpenID Foundation ratified an authentication layer on OAuth 2.0 for websites and applications. JSON-based ID Tokens and discovery gave modern clients another interoperable SSO path.
2014 Feb
OpenID Connect added an interoperable identity layer to OAuth 2.0, including the ID Token and standardized identity claims for relying parties.
2014 Feb 12
NIST released a voluntary framework for improving critical infrastructure cybersecurity. Its five functions gave organizations a common structure for managing cybersecurity risk.
2014 Feb 12
The framework introduced a common risk language built around the Identify, Protect, Detect, Respond, and Recover functions. Profiles connected those outcomes to organizational needs without prescribing one implementation.
2014 Feb 26
The OpenID Foundation ratified an identity layer over OAuth 2.0. ID Tokens, claims, issuer identifiers, and relying-party validation enabled interoperable web sign-in with JSON-based artifacts.
2014 Feb 28
The exchange's collapse made a single custodian's internal key-management failure concrete at scale, years before "not your keys, not your coins" became common practitioner advice.
2014 Apr
CVE-2014-0160 documented a memory-disclosure flaw in affected OpenSSL TLS and DTLS implementations. The event made rapid identification of deployed component versions an operational security need.
2014 Apr
RFC 7208 replaced RFC 4408 and clarified SPF evaluation and deployment. SPF remained evidence about SMTP identities rather than visible From identity.
2014 Apr 7
A flaw in OpenSSL exposed memory from systems using affected releases. The event drew attention to the dependence of major services on critical open source components.
2014 Apr 24
The proposal fixed the derivation path structure almost every HD wallet still uses, letting one seed manage multiple accounts across multiple chains without key collisions.
2014 Apr 24
The Linux Foundation formed an industry-backed effort to identify and fund critical open source projects after Heartbleed.
2014 Jun
Google publicly introduced Kubernetes, bringing a shared orchestration model into the emerging cloud native ecosystem.
2014 Jun 9
Docker Engine 1.0 was released with production support. Container images became a common application delivery artifact, making their contents and distribution a practical security concern.
2014 Jul 29
SatoshiLabs' device moved private key generation and signing into a dedicated offline unit, establishing hardware-backed self-custody as a distinct, purchasable custody model.
2014 Sep
Version 4 refreshed OWASP guidance for structured web application security testing.
2014 Sep
Maintainers listed SAML 2.0 via PicketLink IDP merger work and additional application-server adapters as the next integration priorities.
2014 Sep 10
The first final Keycloak release published stabilized schemas and SPIs for an open-source SSO and identity server.
2014 Oct
Google researchers demonstrated a padding oracle attack against SSL 3.0 CBC mode. All major browsers disabled SSL 3.0 within weeks, effectively ending support for any protocol version below TLS 1.0.
2014 Dec
The Universal Second Factor specification defines a browser-based protocol for using external authenticators like security keys as a second factor. Google and GitHub begin supporting it, demonstrating phishing-resistant authentication in production.
2015
Microsoft LAPS provided a way to rotate distinct local administrator passwords and store them in Active Directory. It addressed the shared-local-password path used for lateral movement.
2015 Mar
DMARC combined SPF and DKIM results with visible From alignment, published policy, and reporting. Domain owners gained a feedback loop for mail using their domains.
2015 Mar
DMARC connected SPF and DKIM results to the visible sender domain, domain policy, and feedback reports. Domain owners gained a coordinated deployment and monitoring mechanism for spoofing defense.
2015 Apr
Microsoft began previewing DLP for SharePoint Online and OneDrive for Business, adding policy evaluation to cloud content stores. Enforcement started to follow data into hosted repositories, not just mail flow.
2015 Apr
The OpenID Foundation introduced conformance profiles and tests for OpenID Providers. Operators gained public implementation evidence beyond a vendor's statement of protocol support.
2015 Apr
Defined a signaling cipher suite value that prevents protocol downgrade attacks by letting a server detect when a client has fallen back to a lower TLS version than the server supports.
2015 May
RFC 7519 defined JSON Web Token claims and compact serialization. Token validation became an explicit API implementation concern.
2015 Jun 22
Industry participants announced the Open Container Project to establish open container format and runtime standards. Docker contributed container format and runtime technology to the project.
2015 Jul
The 1.0 release marked an early production milestone for Kubernetes and made platform controls a practical concern for more teams.
2015 Jul
OCI began work on common container standards. The effort created a shared container-artifact model on which digest-addressed distribution and later signing workflows could converge.
2015 Aug 11
Docker Engine 1.8 introduced trusted pull, push, and build as an opt-in feature. Image integrity and publisher verification became explicit workflow concerns.
2015 Sep
Microsoft began the general rollout of DLP across OneDrive for Business, SharePoint Online, and the Office 2016 desktop apps. Policy tips inside the editing applications brought data-in-use feedback to end users.
2015 Sep
RFC 7636 specified proof key for code exchange. Public clients gained a standardized mitigation for authorization-code interception.
2015 Sep
PKCE bound an authorization-code exchange to the client that began it, strengthening public-client and browser-mediated code flows.
2015 Sep
The IETF standardized HTTP-based user and group management across domains. Provisioning could use a shared schema and protocol independently from the sign-in federation path.
2015 Sep 14
Let's Encrypt placed its first publicly trusted certificate into service using automated software. Public certificate issuance became accessible through an automation-centered CA model.
2015 Sep 22
nginx 1.9.5 added the HTTP/2 module in place of the SPDY module. Protocol support changed request concurrency and expanded the protocol behavior that edge testing needed to cover.
2015 Oct
ASVS 3.0 advanced the use of versioned, testable security requirements in application verification programs.
2016
Google documented deployment experience with dynamic device trust tiers. Zero trust moved from a high-level perimeter critique toward an operated access model.
2016
NIST SP 800-154 described data-centric system threat modeling as a form of risk assessment. It framed the practice around selected data and its attack and defense sides.
2016 Feb
The paper defined hunting as a focused, iterative search for adversaries already inside an organization. It framed hypothesis generation and dedicated analysts as parts of the practice.
2016 Feb 4
Docker Engine 1.10 introduced content-addressable storage for images and layers. Digest-based identity became central to selecting exact image content.
2016 Feb 9
nginx 1.9.11 introduced dynamic modules. Module inventory became more important because the active capability set no longer had to be fixed solely at compile time.
2016 Feb 29
A consensus configuration baseline for a cloud provider, covering logging, identity, and network settings. It became the default first yardstick for whether an account was set up safely, and the check set most posture tools shipped with.
2016 Mar
Kubernetes entered CNCF as an incubating project, anchoring a wider cloud native project ecosystem.
2016 Mar
OWASP SAMM 1.1 updated the community maturity model. It kept the focus on measuring current practice and selecting an improvement roadmap appropriate to organizational context.
2016 Apr
The GDPR was adopted with Article 25 requiring data protection by design and by default. It made technical and organizational measures part of the legal expectation for processing systems.
2016 Apr
NIST summarized the quantum threat, defined the goal of PQC, and emphasized cryptographic agility and infrastructure migration.
2016 Apr
The Auditing Standards Board issued SSAE No. 18, clarifying and recodifying attestation standards into AT-C sections for examinations such as SOC engagements.
2016 May 3
The initiative introduced a badge program that lets projects document security and quality practices against public criteria.
2016 Oct
The in-toto project introduced a framework for securing the software supply chain with signed metadata. It broadened the focus from signing a final artifact to verifying authorized steps and their materials and products.
2016 Oct 4
Red Hat described Red Hat SSO as its supported SAML and OAuth identity product built on upstream Keycloak, replacing earlier PicketLink-based custom IdP work for customer-facing login.
2016 Nov
The publication applied security concepts and principles across standards-based systems engineering processes and the system life cycle.
2016 Dec
The call opened a public evaluation process for quantum-resistant public-key encryption, key-establishment, and signature algorithms.
2017
The AICPA Assurance Services Executive Committee issued the 2017 Trust Services Criteria, renaming the former principles framing, aligning structure with COSO 2013, and strengthening cybersecurity-oriented supplemental criteria used in SOC 2.
2017
The project encoded a repeatable collection of Windows analysis tools and environment configuration for installation inside a virtual machine.
2017
Gartner issued its final Magic Quadrant for Enterprise Data Loss Prevention and replaced it the next year with a Market Guide. The change reflected a market Gartner viewed as mature and increasingly delivered inside email, endpoint, and cloud-access platforms.
2017
The survey documented how practitioners described and organized threat hunting. It made the emerging practice measurable enough to compare approaches and maturity.
2017
Sigma introduced a shared rule format, tools, and collections for describing log detections across analysis platforms. Detection content could be reviewed and translated without beginning in one vendor's query language.
2017
SatoshiLabs published a standard for splitting a seed into a threshold of shares using Shamir's secret sharing, giving self-custody a documented alternative to a single written seed phrase.
2017 Jan
The Sigma project began publishing a generic format for describing log detections. Detection authors gained a shared representation that tooling could translate for different SIEM backends.
2017 Feb
SCPs set organization-level permission guardrails for IAM users and roles in member accounts. They do not grant permissions; they cap the maximum available permissions.
2017 Mar 30
The packaged release reduced setup friction and moved automated sandboxing toward a more maintainable analyst service.
2017 Apr
The RBAC authorizer moved to beta and began to be enabled by default by common provisioning tools. It offered a migration path away from ABAC, whose policies were files on the API server that required a restart to change.
2017 May
npm version 5 introduced package-lock.json as a standardized lockfile feature and made lockfiles the default. Repeatable resolution became normal evidence for reviewing a JavaScript dependency graph.
2017 May
WannaCry remotely compromised systems, encrypted files, and affected organizations in more than 150 countries. It made patching and network exposure central ransomware-resilience concerns.
2017 May 1
SSAE 18 became effective for practitioners' reports dated on or after May 1, 2017, becoming the attestation framework for SOC 1, SOC 2, and SOC 3 examinations.
2017 Jun
NIST updated its digital identity guidelines. It clarified identity proofing, authentication, and federation as distinct concerns that IGA must coordinate with rather than replace.
2017 Jun
NotPetya exploited vulnerabilities, gained privileged rights, and rendered infected Windows computers unusable. The event reinforced that recovery planning must address essential systems, not only user files.
2017 Jun 22
NIST reorganized federal digital-identity guidance around identity proofing, authentication, and federation. The authenticator guidance formalized verifier-impersonation resistance as a design property.
2017 Jun 22
The revision updated the introductory handbook and connected information security principles to modern risk management and control families. It superseded the 1995 edition.
2017 Jul
OCI released version 1.0 of its runtime and image-format specifications. A vendor-neutral image format made digest-addressed container artifacts a shared verification subject.
2017 Aug
Certification expanded from providers to relying parties. Application-side validation and session behavior could now be tested against published conformance profiles.
2017 Sep
NIST published the Application Container Security Guide, documenting container risks across images, registries, orchestrators, containers, and hosts.
2017 Sep
NISTIR 8062 introduced predictability, manageability, and disassociability together with a privacy-risk model based on problematic data actions. It gave engineers a way to translate privacy concerns into system objectives.
2017 Oct
RBAC graduated to stable, fixing Roles, ClusterRoles, and their bindings as the authorization vocabulary. Cluster access design moved from provisioning-time configuration to ordinary API objects that could be reviewed and version-controlled.
2017 Nov
OCI released version 1.0.1 of the Image Specification. A stable format specification gave registries and tools a common model for manifests, configurations, and layers.
2017 Nov 6
A reachable function let a user take ownership of, and then destroy, the shared library contract every affected Parity multisig wallet depended on, making the funds permanently unreachable without any key being stolen.
2017 Dec
NIST began public review of 69 submissions that met its minimum acceptance and submission requirements.
2018
The AICPA issued description criteria for management's SOC 2 system description, separating description evaluation from control evaluation against the Trust Services Criteria.
2018
Chrome required signed certificate timestamps for all publicly trusted certificates. Apple enforced CT for certificates issued after October 2018. Certificate issuance became auditable by design rather than by policy.
2018
Gennaro and Goldfeder's paper "Fast Multiparty Threshold ECDSA with Fast Trustless Setup" gave multi-party computation custody a signing protocol efficient enough for production wallets, ahead of the first commercial MPC custody providers.
2018 Jan
ATT&CK began a public version history with v1.0. Stable versions made it practical to record which technique vocabulary a hunt, analytic, or coverage review used.
2018 Jan
The update emphasized applying security design principles to critical infrastructure systems and corrected the first edition.
2018 Feb
NIST listed research on common measurement problems and solutions, reinforcing the need to distinguish activity counts from useful security measures.
2018 Feb
NIST published SCAP 1.3 as the third revision after version 1.0. The revision continued the standardized assessment model while NIST documented coverage gaps for newer endpoint types.
2018 Mar
CNCF graduated Kubernetes after its incubation period, signaling the maturity of the platform around which many cloud native controls operate.
2018 Apr
Version 1.1 added and clarified self-assessment, supply-chain risk, identity, and coordinated vulnerability disclosure. Security operations could map operational evidence to a refined risk-management framework.
2018 Apr 16
NIST released version 1.1 with refinements for identity, supply-chain risk management, self-assessment, and coordinated vulnerability disclosure. It remained compatible with version 1.0.
2018 Apr 16
Version 1.1 added clearer treatment of self-assessment, identity, supply-chain risk, and vulnerability disclosure. Policy teams gained more explicit connections between organizational outcomes and changing dependencies.
2018 May
The GDPR became applicable across the European Union. Privacy design decisions increasingly needed evidence across deployed systems, vendors, retention paths, and rights-request workflows.
2018 May 25
The European Union's harmonized data-protection rules became applicable across personal-data processing in scope. Policy programs had to connect privacy obligations to internal rules, controls, and evidence across organizational boundaries.
2018 Jun
The specification standardized metadata discovery for authorization servers, including endpoint and signing-related configuration used by clients and relying parties.
2018 Jul
A permissions boundary caps the maximum permissions that identity-based policies can grant to an IAM user or role, enabling delegated identity administration without unbounded privilege escalation.
2018 Aug
Removed RSA key exchange, eliminated CBC ciphers, and reduced the handshake to one round trip. Mandatory forward secrecy and authenticated encryption became baseline properties rather than optional enhancements.
2018 Aug 28
nginx 1.15.3 added the ssl_early_data directive when supported by OpenSSL. TLS hardening therefore continued to depend on the deployed NGINX and cryptographic-library combination rather than on a static configuration recipe.
2018 Sep
MTA-STS defined a policy mechanism for requiring authenticated TLS when mail is delivered to a domain. It strengthened transport protection as a distinct email-security layer.
2018 Oct
The update moved the older site aside and directed users to the newer site and STIX/TAXII data for current content. That made technique data easier to consume in tooling as well as in the browser.
2018 Oct
Project leadership renamed Bro to Zeek while retaining its long-developed network analysis model. The change marked continuity of the monitoring platform and its community under a new name.
2018 Nov
A flaw in how kube-apiserver handled proxied upgrade requests let an authorized client send arbitrary requests to a backend using the API server's own TLS credentials, scoring 9.8 on CVSS v3. It was the first critical Kubernetes CVE to prompt broad emergency patching.
2018 Dec
SP 800-37 Revision 2 added organization preparation, privacy integration, stronger accountability, and continuous monitoring across system and organization levels.
2019
CISA records ABCD ransomware activity in September 2019 as the predecessor to LockBit. The operation's later affiliate model illustrated why defender observations vary across incidents.
2019
OWASP released its first API-specific Top 10. It established a shared vocabulary for broken object authorization and resource limits.
2019 Jan
The first official in-toto Jenkins plugin recorded and signed link metadata for pipeline steps. This made signed supply-chain evidence available inside a common CI system.
2019 Jan
The profile introduced subject identifier attributes to replace inconsistent practices and address weaknesses in persistent NameID usage.
2019 Jan
NIST narrowed the field and increased attention to performance across servers, phones, smart cards, embedded devices, and chips.
2019 Feb
Microsoft announced a cloud-native SIEM built into Azure. The service connected cloud-scale collection and analytics with hunting and automated response.
2019 Feb 5
The exchange's founder had sole control of customer keys and died without sharing access; a later forensic audit found several of the wallets believed to hold customer funds had already been empty for months.
2019 Mar
The IETF standardized an interoperable protocol for certificate authorization, issuance, and revocation. Automated renewal could use a common workflow across compatible clients and authorities.
2019 Mar
The Automatic Certificate Management Environment protocol behind Let's Encrypt reached IETF standard status. Fully automated issuance and renewal drove mass HTTPS adoption from roughly 45% to over 95% of web traffic.
2019 Mar
RFC 8555 standardized ACME interactions for account registration, authorization, certificate orders, finalization, download, renewal, and revocation. It made repeatable issuance workflows a standard protocol concern.
2019 Mar
The Web Authentication API becomes an official W3C Recommendation, enabling browsers and relying parties to use public-key credentials for authentication. This is the moment FIDO moves from a plugin model to a native browser capability.
2019 Mar 4
W3C and the FIDO Alliance announced WebAuthn as a Recommendation and a core FIDO2 component. Web applications gained a standard route to public-key credentials bound to the legitimate verifier.
2019 Mar 4
W3C and the FIDO Alliance finalized Web Authentication as a web standard for public-key credentials. Browsers and platforms gained a common API for phishing-resistant authenticator ceremonies.
2019 Mar 5
The public release provided a free, extensible reverse-engineering suite with disassembly, decompilation, scripting, and collaboration features.
2019 Mar 22
FIPS 140-3 updated requirements for cryptographic module design, implementation, operation, sensitive-parameter management, and lifecycle assurance.
2019 Apr 4
Publishing the source enabled community inspection, patches, extensions, and builds across supported platforms.
2019 May
ARC standardized a way to preserve authentication assessments across intermediaries. It addressed evidence loss in forwarding and mailing-list paths without replacing DMARC.
2019 Jun
Elastic introduced a dedicated SIEM application for host and network investigation workflows. It joined common-schema event data with a security-focused analyst interface.
2019 Jul
A server-side request forgery flaw let an attacker reach the instance metadata service, read the attached role credentials, and use them to copy data on more than one hundred million people from storage. The case became the standard example of how one application bug plus a broad workload identity becomes a data breach.
2019 Aug
Trail of Bits and Atredis Partners assessed eight core components against Kubernetes 1.13.4 and reported 37 findings, alongside a whitepaper and attacker-oriented threat guide. Findings and documentation were released publicly rather than summarized.
2019 Sep
The draft defined logical components, deployment models, use cases, and a migration roadmap in technology-neutral language. Public review began a shared architecture vocabulary beyond individual vendor or enterprise designs.
2019 Oct
OASIS elevated the profile that makes metadata a self-contained source for endpoints, keys, and trust-processing requirements.
2019 Nov
Broadcom completed its 10.7 billion dollar purchase of Symantec's enterprise security business, including Symantec DLP. The former parent renamed itself NortonLifeLock and kept the consumer products.
2019 Nov
Google described Backstory as its flagship hybrid security analytics offering while consolidating Chronicle into Google Cloud. The move placed large-scale security analytics inside a major cloud platform.
2019 Nov
GitHub made automated pull requests for nearest non-vulnerable dependency versions generally available for public repositories. Dependency remediation became part of routine pull-request work.
2019 Nov 19
The metadata service moved to session-authenticated requests with a low IP time-to-live and a request-header requirement, so a forwarded or proxied request can no longer retrieve instance role credentials. It is the direct control response to the previous attack class.
2019 Dec
Uses automated reasoning to identify resources shared outside a defined zone of trust. Later extended with internal access analysis, unused access findings, policy validation, and policy generation.
137 milestones
2020
CWE extended the list beyond software weaknesses to cover recurring hardware security issues and their classifications.
2020
LockBit-named ransomware was first seen on cybercrime forums in January 2020. The service model separated ransomware development from affiliate intrusion activity.
2020
Sigstore began work on accessible signing and transparency services for open source software artifacts.
2020
A cross-practitioner group created the Threat Modeling Manifesto. It articulated shared values, principles, patterns, and anti-patterns for collaborative and continuous practice.
2020 Jan
NIST released a voluntary privacy risk-management framework with a Core and Profiles. Teams could express current and target privacy outcomes and prioritize gaps in a form that fits enterprise risk management.
2020 Jan
SAMM 2 provided a maturity model organized around governance, design, implementation, verification, and operations.
2020 Jan
OWASP SAMM 2.0 provided the current major model release. Its governance, design, implementation, verification, and operations functions support lifecycle-wide assessment.
2020 Jan
OWASP SAMM 2.0 organized improvement around governance, design, implementation, verification, and operations.
2020 Feb
RFC 8737 extended ACME to validate IP address identifiers. It broadened automated certificate issuance beyond DNS identifiers for eligible deployments.
2020 Mar
Microsoft added LDAP channel-binding support and audit events for insecure binds. Administrators could identify compatibility dependencies before hardening directory authentication.
2020 Mar 2
ATT&CK placed phishing under Initial Access and separated delivery through attachments, links, services, and later voice. Defenders gained a shared technique model for coverage and scenario design.
2020 Apr
NIST published secure-development practices intended to integrate with each software development lifecycle implementation.
2020 Apr
The 4.1 update kept the guide current as a testing reference while the project continued toward version 5.
2020 May
Revision 5 expanded treatment of key metadata, access control, identity authentication, inventory, certificates, and current cryptographic guidance.
2020 May
The SPIFFE and SPIRE 1.0 release established a stable milestone for workload identity and identity issuance in dynamic environments.
2020 Jun
GitHub added scheduled Dependabot version updates alongside security updates. Maintaining dependency currency became distinct from responding to disclosed vulnerabilities.
2020 Jun
The assessment guide added a method for evaluating the effectiveness of an information security continuous-monitoring program.
2020 Jul
The first non-beta Enterprise release with sub-techniques made technique descriptions more specific. Hunters could use a more precise behavior label when forming and documenting a hypothesis.
2020 Jul
Seven finalists and eight alternates entered the selection round for deeper public security and performance review.
2020 Aug
The final publication established zero trust tenets, policy engine, policy administrator, policy enforcement point, trust-algorithm inputs, threats, and deployment approaches as a reference architecture.
2020 Aug
The document defined zero trust for implementers: no access granted on network location alone, every request authenticated and authorized against the subject, device, resource, and context. It gave cloud teams a referenceable definition rather than a vendor slogan.
2020 Aug
NIST SP 800-207 described zero trust as moving defenses from static network perimeters toward users, assets, and resources. It formalized the shift from location-based trust to explicit access decisions.
2020 Aug
The guidance shifted access reasoning away from implicit network-location trust toward explicit decisions about users, devices, assets, and resources.
2020 Aug 3
The Linux Foundation consolidated the Core Infrastructure Initiative, the Open Source Security Coalition, and other efforts into the OpenSSF.
2020 Aug 11
NIST SP 800-207 narrowed defenses from broad network perimeters toward resources and removed implicit trust based only on network location. Firewalls remained enforcement points within a wider policy architecture.
2020 Sep
Microsoft added native endpoint enforcement to Microsoft 365 DLP, covering USB copy, network shares, cloud uploads, printing, and clipboard on Windows 10 without a separate agent. Endpoint coverage became part of the same policy set as email and SharePoint.
2020 Sep
Revision 5 consolidated security and privacy controls for systems and organizations and emphasized flexible, customizable use. Official OSCAL formats and crosswalks strengthened machine-readable reuse while preserving mapping limits.
2020 Sep
Revision 5 consolidated security and privacy controls and made control statements outcome-based. IGA programs could align ownership, access review, and evidence with a broader organization-level control framework.
2020 Sep 23
NIST integrated security and privacy controls into one catalog and added a supply-chain risk management control family. The revision broadened control selection beyond isolated technical safeguards.
2020 Oct
The release retired the separate PRE-ATT&CK domain and added reconnaissance and resource development tactics to Enterprise ATT&CK. This expanded the behavior model around activity that precedes access to an environment.
2020 Oct
The publication used risk registers and shared business language to bring cybersecurity risk into enterprise risk management.
2020 Nov
NIST described how cybersecurity risk registers can communicate system and organizational risks into enterprise risk management. The guidance made risk aggregation a governance concern rather than a system-by-system activity.
2021 Apr
The version history records v9.0 as the next major ATT&CK release. Continuing versioned updates kept the behavior vocabulary that hunters use subject to explicit, reviewable change.
2021 Apr
The project deprecated PSP and announced removal in 1.25, citing usability problems that could not be fixed without breaking changes — notably that it was difficult to determine which policy applied to a given Pod.
2021 May
CIS Control 4 placed secure configuration across enterprise assets and software in one maintained process. The scope explicitly included network devices, servers, end-user devices, and other asset classes.
2021 May
The attack temporarily disrupted gasoline delivery across much of the southeastern United States. It showed how a cyber incident can quickly become an operational continuity event.
2021 May
Executive Order 14028 defined an SBOM as a formal record of component details and supply-chain relationships. Component inventory gained a policy role beyond individual vulnerability scans.
2021 May
The order required federal civilian agencies to plan for zero trust architecture. The directive made implementation an accountable government program rather than only an architectural recommendation.
2021 May
Executive Order 14028 directed federal guidance for secure software development practices and supplier attestations. Secure development became a software supply-chain expectation for federal procurement.
2021 May
The order established baseline security standards for software sold to the US government and called for greater software visibility.
2021 May
RFC 8725 documented JSON Web Token best current practices. It emphasized explicit algorithm, issuer, audience, and token-kind checks.
2021 May
RFC 9001 specifies how TLS 1.3 secures QUIC, the UDP-based transport protocol behind HTTP/3. TLS provides the handshake and key schedule while QUIC replaces the record layer with its own packet protection.
2021 May 12
Executive Order 14028 directed the publication of minimum elements for an SBOM. Component inventory became a formal supply-chain security expectation for software producers.
2021 May 12
The order directed federal action on software supply chain security and prompted standards and guidance for secure development and software evidence.
2021 May 12
Executive Order 14028 directed NIST to issue guidance for practices that enhance software supply-chain security and secure development environments.
2021 May 12
Federal agencies were directed to adopt zero-trust architecture, multi-factor authentication, and encryption, and to move to secure cloud services on a fixed schedule. It pulled cloud security requirements from guidance into procurement.
2021 May 19
Sigstore was introduced as a public-good software signing service. Keyless signing and transparent verification became available for software supply-chain artifacts.
2021 Jun
Google introduced SLSA as an end-to-end framework for supply-chain integrity. Dependency vulnerability matching was increasingly placed beside build and publication integrity controls.
2021 Jun
CISA records LockBit 2.0 and its StealBit tool in June 2021. The change reflects the defense problem covered here; restoration alone does not settle data-extortion risk.
2021 Jun
Sigstore established a public trust root for its signing infrastructure. The project advanced an identity-based approach using shared trust services instead of per-project long-lived signer-key distribution.
2021 Jun
SLSA introduced a framework for describing supply-chain integrity practices and verifiable build evidence.
2021 Aug
The two agencies released a cybersecurity technical report describing common threats to Kubernetes environments and the configuration that reduces them. It gave organizations an external, citable baseline rather than vendor guidance.
2021 Oct
HelpSystems, later renamed Fortra, acquired Digital Guardian, one of the last large independent enterprise DLP vendors. Standalone DLP suites kept being absorbed into broader data-security portfolios.
2021 Oct 28
Maintainers published the plan to make a Quarkus-based distribution the default, with simpler configuration and a migration window away from WildFly.
2021 Nov
Generates fine-grained IAM policies from CloudTrail access activity, automating the path from over-permissive starter policies to least-privilege production policies.
2021 Dec
The replacement for PSP arrived as a built-in admission controller driven by namespace labels, applying the Pod Security Standards in enforce, audit, and warn modes.
2021 Dec 10
The remote code execution flaw in Apache Log4j created an urgent need to locate affected versions across deployed software inventories.
2022
Vendor-neutral guidance for secure cloud adoption and migration, covering shared services, zero trust, and continuous posture management. It consolidated a decade of practice into one reference architecture agencies and their vendors could build against.
2022
Version 17 shipped Quarkus as the default distribution and deprecated the WildFly legacy distribution, changing server configuration and container packaging.
2022
Microsoft documented threat modeling as an evolutionary DevOps practice tied to actionable mitigations and implementation tracking. The guidance explicitly extends scope to modern supply-chain and deployment concerns.
2022
Parallel revisions updated implementation guidance for the 2018 SOC 2 description criteria used to evaluate management's system description.
2022
The AICPA published revised points of focus for the 2017 Trust Services Criteria, updating interpretive guidance used when applying the criteria in SOC 2 examinations.
2022 Jan
Memorandum M-22-09 set goals across identity, devices, networks, applications and workloads, and data. Agencies received concrete outcomes for translating the architecture into programs and controls.
2022 Feb
NIST published SP 800-218, Secure Software Development Framework version 1.1. It supplied high-level practices that organizations can integrate into any SDLC and use as a common vocabulary with suppliers.
2022 Feb
NIST published SP 800-218 version 1.1 with secure development practices that include handling third-party software components. Dependency maintenance became part of a documented development lifecycle framework.
2022 Feb
NIST published SSDF 1.1 as high-level secure software development practices that can be integrated into each development lifecycle.
2022 Feb
SP 800-218 replaced the original SSDF white paper and added secure-environment, provenance, and requirements guidance.
2022 Feb 3
NIST SP eight hundred dash two hundred eighteen standardized a core set of secure software development practices, including provenance tasks.
2022 Mar 23
Spear-phishing against a Sky Mavis employee, combined with a validator-signing allowlist grant that was never revoked, gave attackers enough validator signatures to forge withdrawals without touching any smart contract.
2022 Apr
NIST SP 800-40 Revision 4 defined patch management as identifying, prioritizing, acquiring, installing, and verifying updates. This tied update verification to ongoing infrastructure risk reduction.
2022 May 03
Before 1.24 the control plane created a permanent Secret-based token for every ServiceAccount. From 1.24 it does not, leaving projected, short-lived tokens from the TokenRequest API as the default workload credential.
2022 Jun
Project guidance set June 2022 as the end of support for the legacy WildFly distribution after the Quarkus default switch.
2022 Jul
AWS Single Sign-On is repositioned as the recommended workforce identity service, connecting users to AWS accounts and applications through an organization instance.
2022 Jul
NIST selected CRYSTALS-Kyber for general key establishment and Dilithium, FALCON, and SPHINCS+ for signatures.
2022 Aug
ISO 31700 established consumer-protection privacy-by-design requirements and guidance for consumer goods and services. It extended the design focus into organizational processes and product development.
2022 Aug
AWS and partners released OCSF as an open specification for normalizing security telemetry across products and services. It addressed the common-schema stage that enables cross-source analytics.
2022 Aug
Kubernetes 1.25 made Pod Security Admission stable, providing a built-in admission path for Pod Security Standards profiles.
2022 Aug 25
Kubernetes 1.25 shipped PSA as stable and removed PSP entirely, so workload hardening became a namespace label rather than a policy object bound through RBAC. Clusters still using PSP had to migrate before upgrading.
2022 Sep
The second reference architecture organized capabilities and activities for mission systems. It expanded the operational relationships around identity, devices, applications, data, networks, analytics, and automation.
2022 Sep
An attacker flooded a contractor with push notifications until one was approved, then used social engineering via WhatsApp to pressure the approval. The incident becomes the canonical example of push bombing and accelerates adoption of number matching and transaction context in push-based MFA.
2022 Oct
CISA published prioritized baseline practices that organizations can use to track and improve cybersecurity outcomes.
2022 Oct
CISA published implementation guidance for phishing-resistant multifactor authentication. The guidance moved organizations from treating all additional factors alike toward selecting methods that resist impostor verifiers.
2022 Oct
The third edition refreshed the requirements for establishing, implementing, maintaining, and improving an information security management system. It preserved risk-based management while updating the standard's control context.
2022 Oct
ISO published the third edition of ISO/IEC 27001. Organizations applying the standard continued to use a requirements-based ISMS and risk-management approach.
2022 Nov
Provides a managed event data store for querying and analyzing CloudTrail activity events, extending IAM audit capability beyond trail-based delivery to S3.
2022 Nov
The strategy connected department-wide adoption, secured systems, technology acceleration, and enabling processes to a target implementation roadmap.
2022 Nov
Revision 1 updated the engineering guidance and retained design principles as flexible tools for trustworthy secure systems across the life cycle.
2022 Nov
Best Current Practice replacing RFC 7525, mandating TLS 1.2 as the minimum and providing cipher suite guidance that reflects the post-TLS 1.3 landscape. Deprecated TLS 1.0 and 1.1 for all new deployments.
2023
The 2023 edition includes business-flow abuse, server-side request forgery, improper inventory management, and unsafe API consumption.
2023
Wallets generated with Libbitcoin Explorer's bx seed command turned out to use a Mersenne Twister pseudorandom generator seeded with only 32 bits of system time, shrinking the practical key space enough for attackers to find and drain affected wallets.
2023 Mar 1
The EntryPoint contract and bundler infrastructure went live, letting smart contract wallets implement programmable validation such as social recovery and session keys without any change to Ethereum's protocol layer.
2023 Apr
A further third-party audit was published in full, establishing repeated external review as a norm for the project rather than a one-off exercise.
2023 Apr
The model defined traditional, initial, advanced, and optimal stages across five pillars and three cross-cutting capabilities. It gave operators a progression for automation, visibility, and integrated policy.
2023 Apr
SLSA published its first stable version and added explicit verification guidance for provenance. The milestone reinforced that producing signed evidence is insufficient unless consumers compare it with expectations.
2023 Apr
The stable specification defined build integrity levels and provenance requirements for software artifacts.
2023 Apr
Windows LAPS became available on supported Windows client and server platforms through the April 2023 updates. It added a built-in management path for local and DSRM passwords.
2023 Apr 10
The Cloud Native Computing Foundation accepted Keycloak as an incubating project.
2023 Apr 19
SLSA released its first stable version. Provenance moved toward a stable, verifiable contract for build inputs, builder identity, and artifact subjects.
2023 May
The three major platform vendors announce synchronized passkey support across their ecosystems. A 2024 FIDO Alliance survey finds fifty-three percent of people have enabled passkeys on at least one account, signaling the transition from security-key-only FIDO to consumer-scale passwordless authentication.
2023 May 16
The second-generation KMS provider reworked encryption at rest around key hierarchy, rotation, health checks, and observability, addressing the performance limits that discouraged KMS v1 adoption.
2023 May 16
The optional seed-backup service split an encrypted copy of a user's key material across three custodians; critics argued this contradicted the hardware-wallet premise that a key never leaves the device, and Ledger postponed the launch a week later.
2023 May 23
nginx 1.25.0 added experimental HTTP/3 support. Edge review had to account for another transport path and its corresponding configuration and test coverage.
2023 Jun
The advisory documented LockBit activity, affiliate variation, and mitigation recommendations. It connected ransomware response to continual testing of controls against observed attacker techniques.
2023 Jul
The SEC adopted rules requiring covered public companies to describe cybersecurity risk management, strategy, governance, and incident disclosure. Board oversight and management roles became explicit disclosure subjects for those issuers.
2023 Aug
NIST published draft standards for algorithms later named ML-KEM, ML-DSA, and SLH-DSA and invited public feedback.
2023 Sep
CISA set goals for understanding open source dependency prevalence, reducing federal risk, and hardening the wider ecosystem.
2023 Sep
DPoP standardized a proof-of-possession mechanism for OAuth access tokens, addressing replay risk when a token is presented by an unintended party.
2023 Sep
Scattered Spider impersonated an MGM employee over the phone, got the IT help desk to reset MFA, and deployed ransomware across 30+ properties. The $100 million loss demonstrates that MFA protection collapses when help-desk recovery procedures rely on knowledge factors available in breach databases.
2023 Sep
The publication adapted zero trust access control to cloud-native applications across multiple clouds. It added identity-tier and network-tier policies, service meshes, and gateways to the implementation vocabulary.
2023 Sep 30
AICPA & CIMA listed the consolidated 2017 Trust Services Criteria with 2022 revised points of focus as a current free download resource for practitioners and service organizations.
2023 Oct
NIST published a new planning guide focused on organization-wide improvement of cybersecurity log management. The revision reframed log management as a continuing program of generation, transmission, storage, access, and disposal.
2023 Oct
Attackers extracted HAR files containing session tokens from Okta customer support system, bypassing MFA entirely because the tokens represented already-authenticated sessions. The incident affects roughly 18,000 customer accounts and reinforces that session lifecycle management is part of MFA real assurance boundary.
2023 Nov
RFC 9525 updated service-identity verification for TLS. It clarified how clients compare a reference identity with identifiers presented in a certificate.
2023 Nov 15
Red Hat generally available the Red Hat build of Keycloak as the commercial IAM offering based on Quarkus Keycloak, replacing plans for a further Red Hat Single Sign-On major line.
2023 Dec 13
Kubernetes 1.29 marked KMS v2 stable. KMS v1, deprecated in 1.28, was disabled by default from the same release and requires an explicit feature gate to use.
2023 Dec 14
A phished former employee's credentials let attackers publish malicious versions of a widely used wallet-connector npm package, injecting fund-draining code into dozens of applications before Ledger pulled the versions roughly five hours later.
2024
Keycloak added supported lightweight access token behavior so clients can carry fewer JWT claims and use introspection or userinfo for the rest.
2024 Feb
Gmail required bulk senders to use SPF, DKIM, and DMARC, alongside TLS and spam-rate requirements. Authentication became a delivery prerequisite for many senders.
2024 Feb
The update added Govern to the core functions and presented cybersecurity outcomes for organizations of every size and sector.
2024 Feb
CSF 2.0 expanded its audience to all organizations and made governance a separate Function spanning strategy, roles, policy, oversight, and supply-chain risk.
2024 Feb
CSF 2.0 broadened the framework's governance emphasis and refreshed the outcome structure used to relate measures to cybersecurity objectives.
2024 Feb
CSF 2.0 expanded the framework's intended audience and added the Govern function. Network security planning gained a clearer link between technical controls, enterprise risk decisions, and supply-chain context.
2024 Feb 26
NIST released CSF 2.0 for organizations of any sector or size and added the Govern function. The framework now organizes cybersecurity risk outcomes around six concurrent functions.
2024 Feb 26
CSF 2.0 expanded its intended audience to all organizations and added Govern as a distinct function. Policy, roles, oversight, and enterprise risk alignment became more visible across the framework.
2024 Mar
A report to the oss-security mailing list described a backdoor in upstream xz releases that could affect SSH server compromise. The incident showed why known-vulnerability matching alone cannot cover malicious changes in a dependency supply path.
2024 Mar 29
Investigators found malicious code in release tarballs of xz versions five point six point zero and five point six point one, demonstrating a targeted compromise of an upstream release path.
2024 Apr 22
NIST added interim guidance for syncable authenticators such as passkeys. Phishing-resistant authentication became easier to deploy across devices while introducing recovery and synchronization considerations.
2024 Apr 24
Policy rules written in CEL began running inside the API server as a declarative alternative to validating admission webhooks, removing an external HTTP callout from the admission path for many organizational rules.
2024 May
CIS released Controls v8.1 with governance recommendations for policies, procedures, processes, and compliance evidence. The update connected prioritized safeguards more directly to governance practice.
2024 Aug
The first three NIST PQC standards became available for immediate implementation in products, services, and protocols.
2024 Nov
RCPs complement SCPs by setting maximum permissions on resources rather than principals, closing the governance gap for resource-based access across an organization.
2024 Dec
NIST replaced the earlier guide with separate volumes for selecting measures and developing a measurement program.
2025
CISA updated guidance for SBOM data, automation support, practices, processes, coverage, and frequency.
2025 Jan
The guidance consolidated modern OAuth security recommendations, including authorization-code flow, redirect, token, and replay protections relevant to OpenID Connect deployments.
2025 Feb 21
Attackers used a compromised Safe developer's machine to disguise a malicious transaction; Bybit's own account describes signers seeing a masked interface showing the correct address while the actual request changed control of the cold wallet, with no flaw found in the Safe contracts or frontend source code.
2025 May
ASVS 5.0.0 updated the verification standard that organizations use to define and test application security controls.
2025 Jun
NIST SP 800-228 organized controls across pre-runtime and runtime lifecycle stages for cloud-native systems.