Security cheat sheets that tell you what to do first
Each sheet covers one topic. It ranks the actions, sets deadlines, cites its sources and shows when it was last reviewed. When a sheet is past its review date, it says so.
Capability map
Sheets cover 70 of 70 capabilities so far. Each sheet sits in one capability, so the map also shows what is still missing.
- Sheet available
- Being written
- Not covered yet
Governance and regulation 8 of 8
- EU regulation: NIS2, CRA, DORA Map each legal entity and product to NIS2, DORA and the CRA, and set up one process that can report within 24 hours.
- Supplier and third-party risk List every supplier with admin access, tokens or critical data, and make sure you can cut each one off within an hour.
- Security awareness Train five behaviors, make reporting one click and blameless, and track time to report instead of click rates.
- ISMS and ISO 27001 Certify only what customers or regulators ask for, scope all relevant operations and review risks with management at least once a year.
- Cyber insurance Back each questionnaire answer with evidence, call the insurer before any responder and read five clauses before renewal.
- Security metrics and reporting Report about seven outcome measures on one page each quarter, each with its coverage, target and the decision you need.
- Payment fraud Confirm every bank detail change on a number you already have, wait two business days before paying it, and require two signatures at the bank.
- Customer security reviews Answer every questionnaire from one dated evidence pack within five working days, and mark planned controls as planned.
Security leadership 10 of 10
- Security strategy Tie three to five measurable bets to the business plan and a numeric risk appetite on one page; management signs it and reviews it every year.
- Operating model Name one accountable person for each of six core security processes and fit the whole operating model on two pages.
- Security team structure Within 30 days, name a head of security with a deputy and a direct line to management, outside IT operations.
- Maturity assessments Assess against one model every 12 months, rate only what evidence shows and set a target per function, not one score.
- Security program and roadmap Fund 8 to 12 initiatives on one 18-month roadmap, ranked by risk reduction per euro, and steer it monthly and quarterly.
- Security projects Set a coverage target such as 98% and dated exceptions before the pilot, run report-only for at least a week, and check IT projects at kickoff and before go-live.
- Risk register and exceptions Keep 20 to 50 risks with business owners, and let no accepted risk or exception run past 12 months.
- Policies and standards Keep one signed security policy, an acceptable use page and six topic policies of testable rules, each backed by a setting, and review them yearly.
- First 90 days as head of security Listen and fix five basics in month one, measure in month two, and get a strategy and roadmap approved by day 90.
- Audit readiness and evidence Map every control to dated evidence and an owner, and sample your own controls each quarter so auditors find nothing new.
Vulnerabilities and exposure 6 of 6
- Patching Exploited and internet-facing: contain in 24 hours, patch within 72.
- Attack surface management Rebuild your list of internet-facing assets from registrars, DNS, certificate logs and cloud accounts, rescan it every week and give each exposed service an owner.
- Secure configuration Pick one baseline per server platform, audit each risky change for two to four weeks, enforce in rings and check drift weekly.
- Penetration testing Scope tests around identity, internet-facing systems and critical apps, and fix and retest critical and high findings within 30 days, or 14 if internet-facing.
- DNS and domains Put phishing-resistant MFA on every registrar and DNS account this month, registry-lock the domains you sign in and mail with, and send all user DNS through a resolver you control.
- Websites and CMS Turn on automatic updates and admin MFA, and leave PHP 8.2 and Drupal 10 before support ends in December 2026.
Identity and access 5 of 5
- Passkeys and MFA Put admins on security keys or passkeys first, then retire SMS, voice and email codes for everyone else.
- Privileged access List every Tier 0 account, app and server, keep fewer than five Global Administrators and make other admin roles time-limited.
- Joiners, movers and leavers Drive accounts from HR dates, cut every access on the last day, and review guests and dormant accounts every quarter.
- Non-human identities and secrets Give every service account, app secret and API key an owner and a rotation date, and cap Entra app secrets at 180 days.
- Active Directory and Entra Connect Run a free AD assessment this month, close every path an ordinary user has to Domain Admin, and rotate krbtgt every six months.
Data protection 5 of 5
- DLP and sensitivity labels Publish four labels with a default and stop card numbers and IBANs from leaving by email or sharing links.
- Retention and deletion Give every record type a period (in Germany 10 years for books, 8 for vouchers, 6 for letters) and delete whatever has expired each January.
- Encryption and key management Automate certificate renewal before the 100-day limit on 15 March 2027, and inventory your cryptography for the post-quantum move.
- External sharing and collaboration Make Specific people the default link, limit Anyone links to view-only and 30 days or turn them off, and check what's already shared every quarter.
- GDPR security duties Require MFA on every remote login, link each processing record to its systems and keep dated proof that you test your measures.
Cloud and infrastructure 12 of 12
- Cloud configuration Check Microsoft 365 and every cloud account against one free baseline this month, block public storage and long-lived keys at the top, and diff the results every week.
- Edge devices Take management interfaces off the internet, keep 12 months of device logs elsewhere and replace devices before support ends.
- Network segmentation Wall off management and backups first, block SMB and RDP between workstations, and scan from a user laptop every quarter.
- Endpoints and email Run EDR with tamper protection everywhere and put users on standard accounts this month; take every mail domain to DMARC enforcement within 90 days.
- Containers and Kubernetes Make the API server private, enforce Pod Security baseline in every app namespace and upgrade within each version's 12 months of patches.
- OT and industrial systems This month, take every PLC and HMI off the internet, change default passwords and keep offline copies of controller logic.
- Mobile devices Gate every phone in Conditional Access this month; block iOS more than one major release behind and Android older than 14.
- Wi-Fi and network access control Move staff Wi-Fi to device certificates (EAP-TLS) within 6 months; since October 2026 Windows blocks automatic MS-CHAPv2 sign-in.
- Browsers Manage Edge and Chrome centrally, force every update to apply within 72 hours and allow sign-in only with work accounts.
- Macs Enroll every Mac through Apple Business so it can't leave management, and enforce macOS updates within 7 days, or 72 hours when exploited.
- Remote access Close every RDP and SSH port on the internet, require phishing-resistant MFA and a compliant device on every way in, and license one support tool.
- SAP and ERP systems Patch SAP and Oracle every month, exploited flaws on exposed systems within 72 hours, and keep SAP support packages under 24 months old.
Software and supply chain 4 of 4
- Software supply chain Make new package versions wait 3 days, lock every GitHub Action to a commit and publish without long-lived tokens.
- Secure development Publish a disclosure policy, block secrets at push and fix reported flaws within 90 days, or 7 if exploited.
- API security Check the caller's right to each object in code on every request, and replay every call with a second tenant's token before each release.
- CRA for product makers Report exploited flaws within 24 hours now, and give every product a risk assessment, SBOM, support period and CE marking by 11 December 2027.
Secure coding 7 of 7
-
TypeScript and Node.js
Parse every input with a runtime schema, make
anya lint error and check authorization in each handler, not only in middleware. -
Rust
Confine
unsafeto a few reviewed modules, turn on overflow checks in release builds and keep attacker input away from panics. - Python Keep pickle-based loaders away from outside data, pass data as arguments instead of code, and move off Python 3.10, unsupported since 1 October 2026.
- C# and .NET Move off .NET 8 and 9 before support ends on 10 November 2026, never let data pick the type it deserializes into, and require authentication by default.
- Java Never let outside data name the class it becomes, keep input out of queries and expressions, and move off Spring Boot 3.5, whose free fixes ended in June 2026.
- Go Rebuild every binary with Go 1.27.3 or 1.26.10 now and on each point release, gate CI on govulncheck and gosec, and put a timeout and a size limit on every request.
- C and C++ Ship every build with the OpenSSF hardening flags and a bounds-checked standard library (0.3% overhead at Google), fuzz parsers under ASan and write new components in a memory-safe language.
AI 5 of 5
- AI agents Give each agent its own least-privilege identity and a human gate on anything irreversible.
- LLM applications Give staff one approved AI tool and make every AI app retrieve only what the user can already see.
- AI for security operations Start with one frequent task you can check quickly, in an approved tool, and keep it read-only.
- AI governance and the AI Act List every AI system with your role and its risk class; Annex III high-risk duties start 2 December 2027.
- AI coding assistants Use company accounts, require the sandbox with bypass modes off, and have a second person approve every agent pull request.
Detection and response 5 of 5
- Logging and monitoring Send identity, cloud and server logs to a store your admins can't erase, keep 12 months and prove monthly that your alerts fire.
- Incident response Check today that your audit log is on; in an incident, isolate rather than wipe and export the logs within the first hours.
- Threat intelligence Subscribe to CERT-Bund, the KEV catalogs and your vendors' advisories, and give every warning that matches your inventory an owner and a decision within one working day, the same day if it is exploited and exposed.
- SOC and MDR services Have alerts handled 24/7 by someone allowed to isolate devices and disable accounts, and plant a test attack every quarter.
- Canaries and honeytokens Plant five decoys on the paths intruders take, route every trip to someone on call and test each one quarterly.
Resilience and recovery 3 of 3
- Backups Set RPO and RTO per system with its owner, back up SaaS data and configuration too, and restore something every month.
- Ransomware readiness Keep one backup copy attackers can't delete and time a full restore at least once a year.
- Business continuity List the processes that can't stop for a week, give each a written workaround and exercise the plan at least once a year.
Sheets
- Patching Exploited and internet-facing: contain in 24 hours, patch within 72.
- Agentic AI Give each agent its own least-privilege identity and a human gate on anything irreversible.
- Passkeys and MFA Put admins on security keys or passkeys first, then retire SMS, voice and email codes for everyone else.
- Software supply chain Make new package versions wait 3 days, lock every GitHub Action to a commit and publish without long-lived tokens.
- Protecting AI inputs Give staff one approved AI tool and make every AI app retrieve only what the user can already see.
- AI for security teams Start with one frequent task you can check quickly, in an approved tool, and keep it read-only.
- DLP and sensitivity labels Publish four labels with a default and stop card numbers and IBANs from leaving by email or sharing links.
- EU security laws Map each legal entity and product to NIS2, DORA and the CRA, and set up one process that can report within 24 hours.
- Ransomware readiness Keep one backup copy attackers can't delete and time a full restore at least once a year.
- Incident response Check today that your audit log is on; in an incident, isolate rather than wipe and export the logs within the first hours.
- Edge devices Take management interfaces off the internet, keep 12 months of device logs elsewhere and replace devices before support ends.
- Network segmentation Wall off management and backups first, block SMB and RDP between workstations, and scan from a user laptop every quarter.
-
Secure TypeScript
Parse every input with a runtime schema, make
anya lint error and check authorization in each handler, not only in middleware. -
Secure Rust
Confine
unsafeto a few reviewed modules, turn on overflow checks in release builds and keep attacker input away from panics. - Secure Python Keep pickle-based loaders away from outside data, pass data as arguments instead of code, and move off Python 3.10, unsupported since 1 October 2026.
- Privileged access List every Tier 0 account, app and server, keep fewer than five Global Administrators and make other admin roles time-limited.
- Logging and monitoring Send identity, cloud and server logs to a store your admins can't erase, keep 12 months and prove monthly that your alerts fire.
- Cloud configuration Check Microsoft 365 and every cloud account against one free baseline this month, block public storage and long-lived keys at the top, and diff the results every week.
- Endpoints and email Run EDR with tamper protection everywhere and put users on standard accounts this month; take every mail domain to DMARC enforcement within 90 days.
- Supplier and third-party risk List every supplier with admin access, tokens or critical data, and make sure you can cut each one off within an hour.
- Secure development Publish a disclosure policy, block secrets at push and fix reported flaws within 90 days, or 7 if exploited.
- API security Check the caller's right to each object in code on every request, and replay every call with a second tenant's token before each release.
- AI governance and the AI Act List every AI system with your role and its risk class; Annex III high-risk duties start 2 December 2027.
- Attack surface management Rebuild your list of internet-facing assets from registrars, DNS, certificate logs and cloud accounts, rescan it every week and give each exposed service an owner.
- Encryption and key management Automate certificate renewal before the 100-day limit on 15 March 2027, and inventory your cryptography for the post-quantum move.
- Joiners, movers and leavers Drive accounts from HR dates, cut every access on the last day, and review guests and dormant accounts every quarter.
- Backups Set RPO and RTO per system with its owner, back up SaaS data and configuration too, and restore something every month.
- Business continuity List the processes that can't stop for a week, give each a written workaround and exercise the plan at least once a year.
- Retention and deletion Give every record type a period (in Germany 10 years for books, 8 for vouchers, 6 for letters) and delete whatever has expired each January.
- Secure configuration Pick one baseline per server platform, audit each risky change for two to four weeks, enforce in rings and check drift weekly.
- Security awareness Train five behaviors, make reporting one click and blameless, and track time to report instead of click rates.
- Threat intelligence Subscribe to CERT-Bund, the KEV catalogs and your vendors' advisories, and give every warning that matches your inventory an owner and a decision within one working day, the same day if it is exploited and exposed.
- ISMS and ISO 27001 Certify only what customers or regulators ask for, scope all relevant operations and review risks with management at least once a year.
- Penetration testing Scope tests around identity, internet-facing systems and critical apps, and fix and retest critical and high findings within 30 days, or 14 if internet-facing.
- Containers and Kubernetes Make the API server private, enforce Pod Security baseline in every app namespace and upgrade within each version's 12 months of patches.
- OT and industrial systems This month, take every PLC and HMI off the internet, change default passwords and keep offline copies of controller logic.
- Secure C# and .NET Move off .NET 8 and 9 before support ends on 10 November 2026, never let data pick the type it deserializes into, and require authentication by default.
- Secure Java Never let outside data name the class it becomes, keep input out of queries and expressions, and move off Spring Boot 3.5, whose free fixes ended in June 2026.
- Secure Go Rebuild every binary with Go 1.27.3 or 1.26.10 now and on each point release, gate CI on govulncheck and gosec, and put a timeout and a size limit on every request.
- Mobile devices Gate every phone in Conditional Access this month; block iOS more than one major release behind and Android older than 14.
- Cyber insurance Back each questionnaire answer with evidence, call the insurer before any responder and read five clauses before renewal.
- Security metrics and reporting Report about seven outcome measures on one page each quarter, each with its coverage, target and the decision you need.
- DNS and domains Put phishing-resistant MFA on every registrar and DNS account this month, registry-lock the domains you sign in and mail with, and send all user DNS through a resolver you control.
- External sharing and collaboration Make Specific people the default link, limit Anyone links to view-only and 30 days or turn them off, and check what's already shared every quarter.
- SOC and MDR services Have alerts handled 24/7 by someone allowed to isolate devices and disable accounts, and plant a test attack every quarter.
- AI coding assistants Use company accounts, require the sandbox with bypass modes off, and have a second person approve every agent pull request.
- Secure C and C++ Ship every build with the OpenSSF hardening flags and a bounds-checked standard library (0.3% overhead at Google), fuzz parsers under ASan and write new components in a memory-safe language.
- Websites and CMS Turn on automatic updates and admin MFA, and leave PHP 8.2 and Drupal 10 before support ends in December 2026.
- Wi-Fi and network access control Move staff Wi-Fi to device certificates (EAP-TLS) within 6 months; since October 2026 Windows blocks automatic MS-CHAPv2 sign-in.
- Browsers Manage Edge and Chrome centrally, force every update to apply within 72 hours and allow sign-in only with work accounts.
- Payment fraud Confirm every bank detail change on a number you already have, wait two business days before paying it, and require two signatures at the bank.
- Non-human identities and secrets Give every service account, app secret and API key an owner and a rotation date, and cap Entra app secrets at 180 days.
- Macs Enroll every Mac through Apple Business so it can't leave management, and enforce macOS updates within 7 days, or 72 hours when exploited.
- Remote access Close every RDP and SSH port on the internet, require phishing-resistant MFA and a compliant device on every way in, and license one support tool.
- Canaries and honeytokens Plant five decoys on the paths intruders take, route every trip to someone on call and test each one quarterly.
- Customer security reviews Answer every questionnaire from one dated evidence pack within five working days, and mark planned controls as planned.
- GDPR security duties Require MFA on every remote login, link each processing record to its systems and keep dated proof that you test your measures.
- Security strategy Tie three to five measurable bets to the business plan and a numeric risk appetite on one page; management signs it and reviews it every year.
- Operating model Name one accountable person for each of six core security processes and fit the whole operating model on two pages.
- Security team structure Within 30 days, name a head of security with a deputy and a direct line to management, outside IT operations.
- Maturity assessments Assess against one model every 12 months, rate only what evidence shows and set a target per function, not one score.
- Security program and roadmap Fund 8 to 12 initiatives on one 18-month roadmap, ranked by risk reduction per euro, and steer it monthly and quarterly.
- Security projects Set a coverage target such as 98% and dated exceptions before the pilot, run report-only for at least a week, and check IT projects at kickoff and before go-live.
- Risk register and exceptions Keep 20 to 50 risks with business owners, and let no accepted risk or exception run past 12 months.
- Policies and standards Keep one signed security policy, an acceptable use page and six topic policies of testable rules, each backed by a setting, and review them yearly.
- SAP and ERP systems Patch SAP and Oracle every month, exploited flaws on exposed systems within 72 hours, and keep SAP support packages under 24 months old.
- Active Directory and Entra Connect Run a free AD assessment this month, close every path an ordinary user has to Domain Admin, and rotate krbtgt every six months.
- CRA for product makers Report exploited flaws within 24 hours now, and give every product a risk assessment, SBOM, support period and CE marking by 11 December 2027.
- First 90 days as head of security Listen and fix five basics in month one, measure in month two, and get a strategy and roadmap approved by day 90.
- Audit readiness and evidence Map every control to dated evidence and an owner, and sample your own controls each quarter so auditors find nothing new.
How we review
- Ranked, with a skip list
- Every sheet ranks at most five actions and names what you can skip.
- Reviewed every 30 days
- Each sheet is checked against its sources and the latest advisories, regulations and research at least once a month. The review date is on every page and every PDF.
- Every number has a source
- Deadlines and statistics link to the regulation, advisory or study they come from. Where a number is our own recommendation, the sheet says so.