# FirewallSync > Practical cybersecurity writing for engineering teams that ship fast. Articles cover AI security, application and API security, identity and access, cloud security, security operations, and privacy and third-party risk. Each carries publication and update dates. How to use this site as a reference: - Each article has a plain-markdown version: add `index.md` to the article URL (listed below). - All articles with metadata, as JSON: https://firewallsync.com/articles.json - Full text of every article in one file: https://firewallsync.com/llms-full.txt - Rules for citing and reusing our work: https://firewallsync.com/for-ai/ - Sitemap: https://firewallsync.com/sitemap.xml Security advice ages. Check the published and updated dates, and prefer the vendor documentation or standard an article relies on for anything you will act on. ## Start here - [About](https://firewallsync.com/about/index.md): FirewallSync is an independent publication of practical cybersecurity writing for the engineers who have to implement security, not just audit it. - [Editorial policy](https://firewallsync.com/editorial-policy/index.md): The standards FirewallSync holds its writing to: independence, primary sourcing, how claims are verified, code examples, updates, guest posts and how commercial content is labeled. - [Corrections](https://firewallsync.com/corrections/index.md): How FirewallSync corrects errors, and a public log of significant corrections to published articles. - [For AI assistants and developers](https://firewallsync.com/for-ai/index.md): How AI assistants, search tools and developers can read, cite and reuse FirewallSync articles, with machine-readable versions of every article. ## AI Security Prompt injection, MCP servers, AI agents and the data-leakage risks that come with putting LLMs into production. - [European Commission AI Cyberattack: What It Has Confirmed](https://firewallsync.com/posts/european-commission-ai-cyberattack-what-we-know/index.md): The European Commission confirmed an AI-generated cyber campaign, detected October 22, took several apps offline. No staff data breach found so far. (2026-11-21) - [Microsoft agent-framework PyPI Compromise: What We Know](https://firewallsync.com/posts/microsoft-agent-framework-pypi-compromise-1-26-1-1-26-2-what-we-know/index.md): agent-framework 1.26.1 and 1.26.2 on PyPI carried a credential stealer that ran on every Python start. Timeline, IOCs, what is unconfirmed and how to check. (2026-11-19) - [How to Build an AI Security Policy Without Blocking Developers](https://firewallsync.com/posts/how-to-build-an-ai-security-policy-without-blocking-developers/index.md): How to build an AI security policy developers will actually follow: risk-tiered rules, fast approval paths, and concrete guidance instead of blanket restrictions. (2026-11-18) - [Shadow AI: How Employees Accidentally Create Security Gaps With AI Tools](https://firewallsync.com/posts/shadow-ai-how-employees-accidentally-create-security-gaps-with-ai-tools/index.md): Shadow AI explained: how employees pasting company data into unapproved AI tools creates real exposure, and why blocking access doesn't actually solve it. (2026-11-17) - [How to Secure MCP Servers in Production](https://firewallsync.com/posts/how-to-secure-mcp-servers-in-production/index.md): A production checklist for securing MCP servers: authentication, credential scoping, input validation, and monitoring for the specific attack patterns MCP introduces. (2026-11-16) - [MCP Authentication and Authorization: What a Secure Deployment Should Check](https://firewallsync.com/posts/mcp-authentication-and-authorization-what-a-secure-deployment-should-check/index.md): How MCP authentication and authorization actually work under OAuth 2.1: audience binding, the confused deputy problem, and what a secure remote MCP deployment must validate. (2026-11-15) - [MCP Tool Poisoning: How Malicious Instructions Can Hide Inside Trusted Tools](https://firewallsync.com/posts/mcp-tool-poisoning-how-malicious-instructions-can-hide-inside-trusted-tools/index.md): MCP tool poisoning explained: how attackers hide instructions in tool descriptions and parameters, why agents follow them, and how to defend against it. (2026-11-14) - [Uber Driver License Data Stolen in Fireworks AI Breach](https://firewallsync.com/posts/uber-driver-license-data-stolen-fireworks-ai-breach-what-we-know/index.md): Uber says compromised credentials at an AI vendor, reported as Fireworks AI, exposed driver data. State filings list 7,870 people so far. What is confirmed. (2026-11-14) - [MCP Security: What Developers Need to Secure Before Connecting AI to Tools](https://firewallsync.com/posts/mcp-security-what-developers-need-to-secure-before-connecting-ai-to-tools/index.md): MCP security fundamentals: server trust, tool poisoning, credential scope, and the confused deputy problem developers need to address before connecting AI to tools. (2026-11-13) - [Notion AI Chats Exposed in Fireworks AI Breach: What We Know](https://firewallsync.com/posts/notion-ai-chats-exposed-fireworks-ai-breach-what-we-know/index.md): Notion says Notion AI chat transcripts from under 1% of workspaces were exposed in a Fireworks AI breach. What is confirmed, the timeline, and what to check. (2026-11-13) - [Excessive Agency in AI Agents: How Too Much Permission Becomes a Security Risk](https://firewallsync.com/posts/excessive-agency-in-ai-agents-how-too-much-permission-becomes-a-security-risk/index.md): Excessive agency in AI agents explained: the three sources OWASP identifies — excessive functionality, permissions, and autonomy — and how to actually scope each one down. (2026-11-12) - [AI Agent Security: Why Giving an Agent Tools Changes the Threat Model](https://firewallsync.com/posts/ai-agent-security-why-giving-an-agent-tools-changes-the-threat-model/index.md): Why giving an AI agent tool access fundamentally changes its threat model, from a text-generation risk to a real-world action risk, and what that requires defensively. (2026-11-11) - [LLM Data Leakage: How AI Applications Accidentally Expose Sensitive Information](https://firewallsync.com/posts/llm-data-leakage-how-ai-applications-accidentally-expose-sensitive-information/index.md): How LLM applications leak sensitive data in practice — training data exposure, cross-user context bleed, and overshared retrieval — and how to actually prevent it. (2026-11-10) - [Indirect Prompt Injection: The AI Security Problem Hiding in Your Data](https://firewallsync.com/posts/indirect-prompt-injection-the-ai-security-problem-hiding-in-your-data/index.md): Indirect prompt injection explained: how attackers plant instructions in documents, emails, and web pages your AI application will later process on someone else's behalf. (2026-11-09) - [How to Defend LLM Applications Against Prompt Injection](https://firewallsync.com/posts/how-to-defend-llm-applications-against-prompt-injection/index.md): Practical defenses against prompt injection in LLM applications: input handling, output validation, and — most importantly — limiting what a successful attack can actually do. (2026-11-08) - [Prompt Injection Explained: How Attackers Manipulate AI Applications](https://firewallsync.com/posts/prompt-injection-explained-how-attackers-manipulate-ai-applications/index.md): Prompt injection explained: why LLMs can't reliably separate instructions from data, the difference between direct and indirect attacks, and why it's structurally hard to fully fix. (2026-11-07) - [LLM Output Handling: Treat Model Output as Untrusted Input](https://firewallsync.com/posts/llm-improper-output-handling-treat-model-output-as-untrusted-input/index.md): LLM05:2025 improper output handling: why model output must be treated as untrusted input, and tested Python fixes for Markdown/HTML, SQL and shell commands. (2026-10-22) ## AppSec & APIs Securing applications, APIs, webhooks, secrets and the software supply chain, from code review to CI pipelines. - [CSAF VEX Remediations and Threats: What Trivy Gets Wrong](https://firewallsync.com/posts/csaf-vex-remediations-threats-category-product-ids-trivy/index.md): CSAF VEX remediations and threats: 5 remediation categories, restart_required, impact threats per product, and why Trivy v0.76.2 rejects product_groups. (2026-11-21) - [OpenVEX Statement Fields: What Trivy and go-vex Ignore](https://firewallsync.com/posts/openvex-statement-fields-status-notes-action-statement-version-trivy/index.md): OpenVEX statement fields Trivy acts on: status and justification only. status_notes, action_statement, last_updated are ignored; version and supplier dropped. (2026-11-20) - [CVE problemTypes and cweId: Getting CWE From CVE JSON](https://firewallsync.com/posts/cve-problemtypes-cweid-cwe-from-cve-json/index.md): CVE JSON stores CWE in problemTypes descriptions cweId, but 24% of 2026 records have no CNA cweId. Gap sources, CISA-ADP fills, and a parser for every case. (2026-11-15) - [vexctl: Create, Add, Merge and Attest OpenVEX Documents](https://firewallsync.com/posts/vexctl-create-add-merge-attest-openvex-documents/index.md): vexctl creates OpenVEX documents, appends statements with add, merges them as a timeline and wraps them in in-toto attestations. Flags and pitfalls in v0.4.4. (2026-11-12) - [Linux Kernel CVE Records: Read Stable-Branch Affected Ranges](https://firewallsync.com/posts/linux-kernel-cve-records-affected-versions-stable-branches/index.md): Linux kernel CVE records split affected data into git ranges and X.Y.* stable-branch ranges. Read both: 1,056 of 7,987 2026 records need the git entry. (2026-11-07) - [OpenVEX Products and Subcomponents: purl Matching Rules](https://firewallsync.com/posts/openvex-products-subcomponents-purl-matching-trivy/index.md): OpenVEX products and subcomponents decide which findings a VEX statement suppresses. How go-vex and Trivy match purls, versions, qualifiers and timestamps. (2026-11-06) - [CVE packageURL: Join CVE JSON 5.2 Records to SBOM purls](https://firewallsync.com/posts/cve-packageurl-purl-cve-json-5-2-affected-sbom-matching/index.md): CVE JSON 5.2 packageURL: a version-less purl in affected[]. 6,284 of 400,445 records use it. How to normalize it and join it to SBOM purls, with tested Python. (2026-11-05) - [CVE cpeApplicability: CPE Match Nodes, Operators, Ranges](https://firewallsync.com/posts/cve-cpeapplicability-cpe-match-nodes-operators-version-ranges/index.md): cpeApplicability in a CVE JSON record: how nodes, AND/OR operators, negate, vulnerable and versionStart/End bounds combine, with a tested Python evaluator. (2026-11-04) - [CycloneDX VEX: analysis.state and justification to OpenVEX](https://firewallsync.com/posts/cyclonedx-vex-analysis-state-justification-openvex-csaf-mapping/index.md): CycloneDX VEX mapped to OpenVEX and CSAF: analysis.state, justification, response and BOM-Link affects, with a tested Python converter and the gaps that lose data. (2026-11-03) - [GitHub Actions OIDC: Stop Storing Cloud Credentials in CI/CD](https://firewallsync.com/posts/github-actions-oidc-stop-storing-cloud-credentials-in-cicd/index.md): How GitHub Actions OIDC works technically, how to configure the AWS trust relationship, and why short-lived tokens change the actual risk profile of CI/CD credentials. (2026-11-02) - [CVE Affected Versions: lessThan, defaultStatus, versionType](https://firewallsync.com/posts/cve-affected-versions-lessthan-defaultstatus-versiontype/index.md): Read affected versions in a CVE JSON 5 record: lessThan vs lessThanOrEqual, changes, versionType and the defaultStatus fallback, with a tested Python evaluator. (2026-11-02) - [How to Secure GitHub Actions: Permissions, Secrets, and OIDC](https://firewallsync.com/posts/how-to-secure-github-actions-permissions-secrets-and-oidc/index.md): How to secure GitHub Actions: workflow permissions, third-party action risk, secrets scoping, and using OIDC instead of long-lived cloud credentials. (2026-11-01) - [Escape User Input in Regex and SQL LIKE: Tested Fixes](https://firewallsync.com/posts/escape-user-input-regex-sql-like/index.md): Escape user text before it enters a regex or LIKE pattern: re.escape, RegExp.escape, regexp.QuoteMeta, and LIKE with an ESCAPE clause. Tested code inside. (2026-11-01) - [Dependency Confusion: How Package Managers Can Become an Attack Path](https://firewallsync.com/posts/dependency-confusion-how-package-managers-can-become-an-attack-path/index.md): How dependency confusion attacks work, why they compromised Apple, Microsoft, and PayPal without a single CVE, and how to actually close the gap. (2026-10-31) - [User-Supplied Regex: How to Run It Without ReDoS](https://firewallsync.com/posts/user-supplied-regex-redos-safe-engines/index.md): To run user-supplied regex safely, use a linear-time engine such as RE2, cap pattern length, and isolate backtracking engines behind a timeout. Tested code. (2026-10-31) - [Software Supply Chain Attacks: Where Modern Build Pipelines Break](https://firewallsync.com/posts/software-supply-chain-attacks-where-modern-build-pipelines-break/index.md): Software supply chain attacks explained: where modern build pipelines actually break, from dependency resolution to CI runners to build-time script execution. (2026-10-30) - [Secure File Uploads in Node.js: A Tested Express Setup](https://firewallsync.com/posts/secure-file-upload-nodejs-express-multer/index.md): Secure file upload in Node.js: Express and Multer limits, magic-byte allowlist, random names, storage outside the webroot and safe download headers, tested. (2026-10-30) - [Node.js Decompression Bombs: zlib Limits That Work](https://firewallsync.com/posts/nodejs-decompression-bomb-zlib-limits/index.md): Node.js decompression bombs: maxOutputLength works for gunzipSync but streams ignore it. Tested limits for zlib, Brotli, zstd, Express and fetch(). (2026-10-29) - [PHP session_regenerate_id: Stop Session Fixation Right](https://firewallsync.com/posts/php-session-regenerate-id-stop-session-fixation/index.md): PHP session_regenerate_id done right: rotate before setting auth, keep old IDs on a timer, enforce idle and absolute timeouts. Tested code for PHP 8.3. (2026-10-28) - [php.ini Security Hardening: Production Settings That Matter](https://firewallsync.com/posts/php-ini-security-hardening-production-settings/index.md): php.ini hardening: the settings PHP's production template leaves open, tested examples, where to set them so apps can't override them, and what not to rely on. (2026-10-27) - [Mass Assignment: How to Stop Clients Setting role=admin](https://firewallsync.com/posts/mass-assignment-vulnerability-how-to-stop-clients-setting-role-admin/index.md): Mass assignment explained: how auto-binding lets clients set role or owner fields, OWASP API3:2023, and tested fixes in Python, Spring and Rails. (2026-10-22) - [Webhook Security: Signatures, Replay Protection, Idempotency](https://firewallsync.com/posts/webhook-security-hmac-signatures-timestamps-and-replay-protection/index.md): Webhook security: verify HMAC signatures on the raw body, reject stale or replayed deliveries, dedupe by event ID. Stripe, GitHub and Shopify compared, with tested code. (2026-10-19) - [JWT Security: 9 Mistakes That Can Turn Tokens Into an Attack Path](https://firewallsync.com/posts/jwt-security-9-mistakes-that-can-turn-tokens-into-an-attack-path/index.md): 9 real JWT security mistakes — algorithm confusion, the alg:none bypass, missing revocation, and more — with the fixes that actually close each one. (2026-10-17) - [IDOR Vulnerabilities: How to Find and Fix Insecure Direct Object References](https://firewallsync.com/posts/idor-vulnerabilities-how-to-find-and-fix-insecure-direct-object-references/index.md): How to find and fix IDOR vulnerabilities: testing methodology, why sequential IDs make exploitation easier, and how to enforce object-level authorization correctly. (2026-10-16) - [Broken Access Control: Real-World Examples and How to Prevent It](https://firewallsync.com/posts/broken-access-control-real-world-examples-and-how-to-prevent-it/index.md): Broken access control tops the OWASP Top 10. Real-world patterns — IDOR, missing function-level checks, privilege escalation — and how to prevent them. (2026-10-15) - [How API Rate Limiting Actually Works—and Where It Fails](https://firewallsync.com/posts/how-api-rate-limiting-actually-works-and-where-it-fails/index.md): How API rate limiting actually works: fixed window, sliding window, and token bucket algorithms compared, and where rate limiting fails in practice. (2026-10-14) - [The Most Common API Security Misconfigurations and How to Fix Them](https://firewallsync.com/posts/the-most-common-api-security-misconfigurations-and-how-to-fix-them/index.md): The most common API security misconfigurations — verbose errors, permissive CORS, exposed debug endpoints — and the fixes that actually close them. (2026-10-13) - [Cosign Container Image Signing: Keyless Signing in CI and Why Verification Must Pin an Identity](https://firewallsync.com/posts/cosign-container-image-signing-keyless-signing-in-ci-and-why-verification-must-pin-an-identity/index.md): How to sign container images with cosign keyless signing in GitHub Actions and verify them with --certificate-identity and --certificate-oidc-issuer, plus what the August 2026 cosign verify-blob advisory (GHSA-fx35-mq7g-6g98) means for you. (2026-10-13) - [VEX Explained: What a "Not Affected" Statement Means and How to Read One](https://firewallsync.com/posts/vex-explained-what-a-not-affected-statement-means-and-how-to-read-one/index.md): VEX (Vulnerability Exploitability eXchange) explained: CISA's four statuses and five not-affected justifications, how OpenVEX and CSAF encode them, and how to decide whether to trust a VEX statement when triaging scanner findings. (2026-10-13) - [How to Secure a Public REST API: A Production Checklist](https://firewallsync.com/posts/how-to-secure-a-public-rest-api-a-production-checklist/index.md): A production checklist for securing a public REST API: authentication, rate limiting, input validation, and the access control gaps that get exploited most. (2026-10-12) - [SLSA Build Levels and Provenance Attestations: What They Prove and What They Don't](https://firewallsync.com/posts/slsa-build-levels-and-provenance-attestations-what-they-prove-and-what-they-dont/index.md): SLSA Build L1, L2 and L3 explained: what provenance attestations prove, what they cannot, how Sigstore signing works, and how to verify GitHub artifact attestations with gh attestation verify. (2026-10-12) - [API Authentication: API Keys vs OAuth vs JWT](https://firewallsync.com/posts/api-authentication-api-keys-vs-oauth-vs-jwt/index.md): API keys, OAuth, and JWTs solve different problems. A practical comparison of what each is actually for, and where teams commonly pick the wrong one. (2026-10-11) - [SBOM Minimum Elements 2026: 17 Fields and What Changed](https://firewallsync.com/posts/sbom-minimum-elements-2026-what-cisa-and-partners-changed-from-the-2021-ntia-baseline/index.md): CISA's 2026 SBOM Minimum Elements list 17 data fields, ten new, including component hash and license. What changed from NTIA 2021, Coverage, SPDX and CycloneDX. (2026-10-11) - [HTTP Security Headers Beyond CSP: HSTS, nosniff, Referrer-Policy and Permissions-Policy Explained](https://firewallsync.com/posts/http-security-headers-hsts-nosniff-referrer-policy-and-permissions-policy-explained/index.md): What HSTS, X-Content-Type-Options, Referrer-Policy and Permissions-Policy do, the values OWASP recommends, the HSTS preload requirements, and which old headers to stop sending. (2026-10-11) - [Burp Suite vs OWASP ZAP: Which Web App Scanner Fits Your Workflow](https://firewallsync.com/posts/burp-suite-vs-owasp-zap-which-web-app-scanner-fits-your-workflow/index.md): Burp Suite vs OWASP ZAP compared: manual testing workflow versus automation-first design, licensing cost, and which fits a small team's actual testing needs. (2026-10-10) - [Content Security Policy: A Strict Nonce-Based Policy and How to Roll It Out Safely](https://firewallsync.com/posts/content-security-policy-a-strict-nonce-based-policy-and-how-to-roll-it-out-safely/index.md): How to write a strict Content Security Policy with nonces, what strict-dynamic and unsafe-inline do, and how to deploy with Report-Only and reporting endpoints. (2026-10-10) - [CORS Misconfiguration: What Access-Control-Allow-Origin Actually Permits](https://firewallsync.com/posts/cors-misconfiguration-what-access-control-allow-origin-actually-permits/index.md): CORS misconfiguration explained: what Access-Control-Allow-Origin with credentials allows, the origin-matching bugs attackers exploit, and a tested fix. (2026-10-08) - [How to Secure OAuth Tokens in Production](https://firewallsync.com/posts/how-to-secure-oauth-tokens-in-production/index.md): How to secure OAuth 2.0 tokens in production: PKCE, refresh token rotation, sender-constrained tokens, and the mistakes RFC 9700 was written to stop. (2026-10-07) - [CSRF Protection: SameSite Cookies, Tokens and Fetch Metadata Compared](https://firewallsync.com/posts/csrf-protection-samesite-cookies-tokens-and-fetch-metadata-compared/index.md): CSRF protection compared: what SameSite=Lax leaves open, when you still need CSRF tokens, and how to reject cross-origin requests with Sec-Fetch-Site. (2026-10-07) - [How to Detect and Rotate Leaked API Keys Before Attackers Use Them](https://firewallsync.com/posts/how-to-detect-and-rotate-leaked-api-keys-before-attackers-use-them/index.md): How to detect leaked API keys across GitHub, logs, and client bundles, and rotate them safely without breaking the services that depend on them. (2026-10-05) - [Argon2id vs bcrypt vs scrypt: OWASP Parameters to Use](https://firewallsync.com/posts/password-hashing-argon2id-vs-bcrypt-vs-scrypt-which-to-use-and-with-what-parameters/index.md): Argon2id vs bcrypt vs scrypt: Argon2id at 19 MiB, 2 iterations, p=1 (OWASP) for new systems, bcrypt at cost 10+ (72-byte limit), and rehash on login. (2026-10-04) - [SSRF Explained: How Server-Side Request Forgery Works and How to Prevent It](https://firewallsync.com/posts/ssrf-explained-how-server-side-request-forgery-works-and-how-to-prevent-it/index.md): SSRF prevention for engineers: how server-side request forgery reaches cloud metadata, why deny lists fail, and how to layer validation, egress and IMDSv2. (2026-10-03) - [The Vulnerability Backlog That Never Shrinks](https://firewallsync.com/posts/the-vulnerability-backlog-that-never-shrinks/index.md): Vulnerability management backlogs keep growing because most programs prioritize by CVSS score alone. A better way to triage what actually gets fixed. (2026-10-01) - [Dependency Audits Without Slowing Down Releases](https://firewallsync.com/posts/dependency-audits-without-slowing-down-releases/index.md): Software supply chain security doesn't require reviewing every dependency manually. A tiered audit approach that keeps release velocity intact. (2026-09-29) - [Container Image Scanning: What CI Pipelines Still Miss](https://firewallsync.com/posts/container-image-scanning-what-ci-pipelines-still-miss/index.md): Container image scanning in CI catches CVEs but misses config drift and runtime secrets. Here's what to add to close the gap. (2026-09-28) - [The API Key Mistakes That Keep Making Breach Reports](https://firewallsync.com/posts/the-api-key-mistakes-that-keep-making-breach-reports/index.md): Why leaked API keys keep showing up in breach reports despite better secrets scanning, and the three preventable mistakes behind most of them. (2026-08-24) ## Identity & Access Authentication, MFA, passkeys, session security and least-privilege access for people and machines. - [How Session Hijacking Works Even After MFA](https://firewallsync.com/posts/how-session-hijacking-works-even-after-mfa/index.md): How session hijacking actually works after MFA succeeds — infostealer malware, XSS-based cookie theft, and AiTM relay — and why each bypasses MFA differently. (2026-11-21) - [Why SMS MFA Is Being Replaced—and What to Use Instead](https://firewallsync.com/posts/why-sms-mfa-is-being-replaced-and-what-to-use-instead/index.md): Why SMS MFA is being phased out — SIM swapping, SS7 interception, and real-time phishing relay — and what NIST and regulators now recommend instead. (2026-11-20) - [Phishing-Resistant MFA: Passkeys vs FIDO2 Security Keys](https://firewallsync.com/posts/phishing-resistant-mfa-passkeys-vs-fido2-security-keys/index.md): Passkeys vs FIDO2 security keys: both are phishing-resistant by the same underlying protocol, but they differ in storage, portability, and rollout tradeoffs. (2026-11-19) - [Maileva Data Breach: La Poste Says 22 Million Hit](https://firewallsync.com/posts/maileva-data-breach-la-poste-22-million-addresses-what-we-know/index.md): La Poste says Maileva lost names and postal addresses of 22 million people in September. Bank details not affected. Confirmed facts, timeline and checks. (2026-11-16) - [DigiCert Data Breach: Self-Registered Accounts Read ID Files](https://firewallsync.com/posts/digicert-data-breach-self-registration-archived-customer-data/index.md): DigiCert says self-registered accounts on an internet-exposed internal system read archived customer data and some ID files in 2026. CA systems unaffected. (2026-11-08) - [Non-Human Identities: The Security Problem Behind Service Accounts and AI Agents](https://firewallsync.com/posts/non-human-identities-the-security-problem-behind-service-accounts-and-ai-agents/index.md): Non-human identities — service accounts, API keys, AI agents — now outnumber human users in most environments, but get a fraction of the identity governance. (2026-11-05) - [Kubernetes Service Account Tokens: Retire Legacy Secrets](https://firewallsync.com/posts/kubernetes-service-account-tokens-bound-vs-legacy-secrets/index.md): Bound Kubernetes service account tokens expire and die with their Pod; Secret-based ones never expire. How to find, trace and retire legacy tokens. (2026-10-24) - [Kubernetes RBAC Audit: 11 Permissions That Escalate Access](https://firewallsync.com/posts/kubernetes-rbac-audit-11-permissions-that-escalate-access/index.md): Kubernetes RBAC audit: the 11 permissions the Kubernetes docs flag as privilege-escalation risks, why each is dangerous, and a tested script to find them. (2026-10-22) - [What Is Token Theft and Why MFA Doesn't Always Stop It?](https://firewallsync.com/posts/what-is-token-theft-and-why-mfa-doesnt-always-stop-it/index.md): Token theft explained: how adversary-in-the-middle attacks steal session cookies after MFA succeeds, and what detection actually needs to catch it. (2026-10-08) - [1Password vs Bitwarden vs Vaultwarden: Choosing a Password Manager for a Small Team](https://firewallsync.com/posts/1password-vs-bitwarden-vs-vaultwarden-choosing-a-password-manager-for-a-small-team/index.md): 1Password vs Bitwarden vs Vaultwarden compared for a small team: managed vs self-hosted tradeoffs, admin features, and which fits different team sizes and risk tolerances. (2026-10-08) - [Passkeys vs Passwords: What Actually Changes for Security Teams?](https://firewallsync.com/posts/passkeys-vs-passwords-what-actually-changes-for-security-teams/index.md): Passkeys vs passwords: how FIDO2's origin binding removes phishing as an attack path, and where recovery and enrollment gaps can undo that protection. (2026-10-06) - [ZITADEL Account-Takeover Flaws CVE-2026-105207, -105209 and -105215: Fixed Versions and What to Check](https://firewallsync.com/posts/zitadel-account-takeover-cve-2026-105207-cve-2026-105209-cve-2026-105215-fixed-versions/index.md): ZITADEL CVE-2026-105207, CVE-2026-105209 and CVE-2026-105215: affected 3.x and 4.x versions, the minimum fixed releases, workarounds, and how to check whether accounts were taken over. (2026-10-06) - [MFA Fatigue Attacks: What Actually Stops Them](https://firewallsync.com/posts/mfa-fatigue-attacks-what-actually-stops-them/index.md): MFA fatigue attacks exploit push notifications, not passwords. Here's why number matching and phishing-resistant MFA actually stop them. (2026-09-25) - [Least-Privilege Access Controls That Don't Slow Teams Down](https://firewallsync.com/posts/least-privilege-access-controls-that-dont-slow-teams-down/index.md): How to roll out least-privilege access without slowing engineers down: start from real usage data, phase the rollout, and make access requests fast enough that nobody routes around them. (2026-08-01) ## Cloud Security Cloud IAM, workload identity, misconfigurations and zero trust, with a focus on what small teams can actually run. - [Trivy --vex oci: OpenVEX Attestations on OCI Images](https://firewallsync.com/posts/trivy-vex-oci-openvex-attestations-cosign-attest/index.md): Trivy --vex oci reads OpenVEX attestations from OCI referrers or cosign .att tags but does not verify signatures. How discovery works and how to verify first. (2026-11-11) - [What Is Workload Identity and Why Should You Stop Using Static Cloud Keys?](https://firewallsync.com/posts/what-is-workload-identity-and-why-should-you-stop-using-static-cloud-keys/index.md): Workload identity explained: how it replaces static cloud keys with short-lived, automatically issued credentials, and how to actually migrate to it. (2026-11-06) - [How to Audit Unused Cloud Accounts, Roles, and Service Identities](https://firewallsync.com/posts/how-to-audit-unused-cloud-accounts-roles-and-service-identities/index.md): How to audit unused cloud accounts, roles, and service identities systematically, using activity data rather than manual review, before they become someone else's access. (2026-11-04) - [Cloud IAM vs Network Security: Why Identity Has Become the New Perimeter](https://firewallsync.com/posts/cloud-iam-vs-network-security-why-identity-has-become-the-new-perimeter/index.md): Why identity has become the primary security boundary in cloud environments, and where teams still over-invest in network controls at the expense of IAM. (2026-11-03) - [Kubernetes Audit Log Detections: 8 Rules We Tested](https://firewallsync.com/posts/kubernetes-audit-log-detections-8-rules-tested/index.md): Kubernetes audit log detections for exec, host-access pods, cluster-admin bindings, Secret sweeps, tokens and impersonation, tested on kube-apiserver v1.34.1. (2026-10-26) - [Kubernetes Audit Policy: What to Log, at What Level](https://firewallsync.com/posts/kubernetes-audit-policy-what-to-log-and-at-what-level/index.md): A Kubernetes audit policy decides what kube-apiserver records. A tested six-rule policy, why rule order can leak Secrets, and the jq queries that use the log. (2026-10-25) - [Kubernetes Secrets Encryption at Rest: What It Protects](https://firewallsync.com/posts/kubernetes-secrets-encryption-at-rest-what-it-protects/index.md): Kubernetes Secrets encryption at rest protects etcd data, not API readers or Pod creators. What each provider stops, how to verify it, and a config checker. (2026-10-23) - [Kubernetes NetworkPolicy Default Deny: A Safe Rollout](https://firewallsync.com/posts/kubernetes-networkpolicy-default-deny-safe-rollout/index.md): Kubernetes NetworkPolicy default deny explained: how isolation works, why DNS breaks, the both-ends rule, selector traps and a safe rollout order. (2026-10-22) - [Kubernetes MutatingAdmissionPolicy: CEL Mutations with Apply Configuration or JSON Patch, and When a Webhook Is Still Needed](https://firewallsync.com/posts/kubernetes-mutatingadmissionpolicy-cel-mutations-apply-configuration-or-json-patch-and-when-a-webhook-is-still-needed/index.md): Kubernetes MutatingAdmissionPolicy explained: stable since v1.36, policy and binding resources, ApplyConfiguration versus JSONPatch mutations, reinvocationPolicy, failurePolicy, matchConditions, exempt kinds, how it differs from mutating webhooks, and a cautious rollout, based on the v1.37 documentation. (2026-10-18) - [Kubernetes ValidatingAdmissionPolicy: CEL Rules for Registry Allowlists and Memory Limits, with a Warn-First Rollout](https://firewallsync.com/posts/kubernetes-validatingadmissionpolicy-cel-rules-for-registry-allowlists-and-memory-limits-with-a-warn-first-rollout/index.md): Kubernetes ValidatingAdmissionPolicy explained: policy and binding resources, CEL expressions, Deny, Warn and Audit actions, failurePolicy, matchConditions, an image-registry allowlist and a memory-limit rule, and a warn-first rollout, based on the Kubernetes v1.37 documentation. (2026-10-17) - [Kubernetes Pod Security Admission: Namespace Labels, Modes and a Safe Rollout from Warn to Enforce](https://firewallsync.com/posts/kubernetes-pod-security-admission-namespace-labels-modes-and-a-safe-rollout-from-warn-to-enforce/index.md): Kubernetes Pod Security Admission explained: privileged, baseline and restricted levels, enforce, audit and warn modes, namespace labels, exemptions, a dry-run rollout plan and a restricted-compliant pod example, based on the Kubernetes v1.37 documentation. (2026-10-15) - [Verify Signed Container Images in Kubernetes with Sigstore policy-controller: Keyless Policy and Safe Rollout](https://firewallsync.com/posts/verify-signed-container-images-in-kubernetes-sigstore-policy-controller-keyless-policy-and-rollout/index.md): How to enforce cosign signatures in Kubernetes with Sigstore policy-controller: namespace opt-in, a keyless ClusterImagePolicy pinned to a GitHub Actions workflow, warn-mode rollout, no-match-policy and webhook failure-policy risks. (2026-10-14) - [How to Find Overprivileged AWS IAM Users and Roles](https://firewallsync.com/posts/how-to-find-overprivileged-aws-iam-users-and-roles/index.md): How to find overprivileged AWS IAM users and roles using Access Analyzer, CloudTrail activity, and policy comparison — before an incident finds them for you. (2026-10-10) - [AWS IAM Least Privilege: A Practical Guide to Finding Excess Permissions](https://firewallsync.com/posts/aws-iam-least-privilege-a-practical-guide-to-finding-excess-permissions/index.md): A practical guide to AWS IAM least privilege: how to find unused permissions with IAM Access Analyzer and safely tighten policies without breaking access. (2026-10-09) - [S3 Block Public Access: What the Four Settings Do and How to Enforce Them](https://firewallsync.com/posts/s3-block-public-access-what-the-four-settings-do-and-how-to-enforce-them/index.md): What the four S3 Block Public Access settings do, which one wins when they overlap, and how to enforce them across an AWS account or organization. (2026-10-08) - [Cloud Misconfiguration Checklists Don't Work — Here's What Does](https://firewallsync.com/posts/cloud-misconfiguration-checklists-dont-work-heres-what-does/index.md): Cloud misconfiguration is still the leading cause of cloud breaches. Static checklists miss drift — here's what to run instead. (2026-10-03) ## Security Operations Incident response, logging, alerting, backups and the processes that keep security work from stalling. - [Chase, Visa, Mastercard Vendor Breach: What We Know](https://firewallsync.com/posts/chase-visa-mastercard-third-party-vendor-breach-what-we-know/index.md): Chase, Visa and Mastercard say vendors were breached and some names and emails may be exposed, not card data. What each firm said and what is unconfirmed. (2026-11-20) - [Public PoC CVEs: Pull All 47,926 SSVC poc Records](https://firewallsync.com/posts/public-poc-cves-cisa-adp-ssvc-exploitation-poc-epss/index.md): SSVC Exploitation poc flags 47,926 CVEs with a public PoC in CISA-ADP data. Pull them to CSV, slice by Automatable and Technical Impact, and join EPSS. (2026-11-19) - [Equinor Cyberattack: What the Energy Giant Has Confirmed](https://firewallsync.com/posts/equinor-cyberattack-it-systems-what-we-know/index.md): Equinor says an ongoing cyberattack hit certain IT systems on Nov 17. Production unaffected, no sign of data theft so far. Confirmed vs unknown, and lessons. (2026-11-18) - [KEV dueDate: 3, 14 or 21 Days After dateAdded, 2021-2026](https://firewallsync.com/posts/kev-duedate-days-after-dateadded-3-14-21-day-deadlines/index.md): KEV dueDate is now 3 or 14 days after dateAdded; it was 21 days from 2022 to early 2026. Counts by year, forensicTriage link, edited due dates, and a script. (2026-11-18) - [Coles Cyber Incident: What the Supermarket Has Confirmed](https://firewallsync.com/posts/coles-cyber-security-incident-what-we-know/index.md): Coles told the ASX on November 16 it is investigating a cyber incident. Stores and online run normally; no evidence so far of data theft. Confirmed vs unknown. (2026-11-17) - [KEV in CVE Records: Audit of All 1,781 CISA-ADP kev Blocks](https://firewallsync.com/posts/kev-in-cve-records-cisa-adp-kev-block-full-catalog-audit/index.md): KEV in CVE records: 1,777 of 1,781 KEV CVEs carry a matching CISA-ADP kev block. 2 lack one, 2 have a different dateAdded, removed CVEs lose theirs. Script. (2026-11-17) - [CVE Exploitation Alerts: Diff CISA-ADP KEV and SSVC Data](https://firewallsync.com/posts/cve-exploitation-alerts-cisa-adp-kev-ssvc-cvelistv5-diff/index.md): Alert on CVE exploitation by diffing CISA-ADP kev and SSVC Exploitation. 30 days of cvelistV5 data: every new active was a KEV CVE; 2 KEV adds lacked a block. (2026-11-16) - [ScreenConnect SCKit Worm via RMM+ Extension: What We Know](https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/index.md): Huntress counted 288 hosts in 48 orgs, then 205 in 41, hit by rogue ScreenConnect clients tied to the RMM+ extension. Confirmed facts, timeline and checks. (2026-11-15) - [CVSS v4 Supplemental Metrics in CVE Records: Who Sets Them](https://firewallsync.com/posts/cvss-v4-supplemental-metrics-in-cve-records-automatable-provider-urgency/index.md): CVSS v4 Supplemental metrics appear in only 3.4% of CNA v4.0 scores in CVE records, mostly from Juniper and Palo Alto. Field names, values and a parser. (2026-11-14) - [CVE JSON CVSS Metrics: cvssV4_0, cvssV3_1, baseScore Trap](https://firewallsync.com/posts/cve-json-cvss-metrics-cvssv4-0-cvssv3-1-basescore-trap/index.md): CVE JSON metrics: 31.3% of 2026 CVEs carry a CNA cvssV4_0 score, 21.1% no CNA CVSS at all, and baseScore can hide Threat metrics. How to pick one score safely. (2026-11-13) - [Maersk Cyberattack: Data Stolen From Acquired Legacy System](https://firewallsync.com/posts/maersk-cyberattack-legacy-system-data-theft-what-we-know/index.md): Maersk confirmed data was extracted from a legacy system from a past acquisition on Nov 11, 2026. What is confirmed, what WhiteArmor claims, what to check. (2026-11-12) - [N-able N-central Offline After Able2Shell Zero-Days](https://firewallsync.com/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/index.md): N-able pulled hosted N-central offline after Able2Shell exploits went public Nov 8. Seven CVEs, a hotfix, no confirmed customer compromise. What to check. (2026-11-11) - [Vanderbilt BYOD Ransomware Attack: What We Know So Far](https://firewallsync.com/posts/vanderbilt-university-byod-ransomware-attack-what-we-know/index.md): Vanderbilt ordered devices shut down on Nov 9 after a cyberattack claimed by the BYOD ransomware gang, its third US university in a month. Confirmed vs claimed. (2026-11-10) - [KEV knownRansomwareCampaignUse: 114 Unknown-to-Known Flips](https://firewallsync.com/posts/kev-knownransomwarecampaignuse-unknown-to-known-flips/index.md): KEV knownRansomwareCampaignUse flips from Unknown to Known silently: 114 times since Jan 2025, none reversed. Lag data, vendors and a script to catch flips. (2026-11-10) - [Supermarket Freezer Hacks: What the CISA-FBI Warning Says](https://firewallsync.com/posts/supermarket-freezer-hacks-refrigeration-controllers-cisa-fbi-warning/index.md): Supermarket freezer hacks: attackers set refrigeration controllers to heat in France, then Belgium and Sweden. What CISA and the FBI advise operators to do. (2026-11-09) - [KEV Time to Listing: CVE datePublished to dateAdded](https://firewallsync.com/posts/kev-time-to-listing-cve-published-to-dateadded-days-by-vendor/index.md): KEV time to listing: for CVEs added in 2026, CISA's dateAdded trails the record's datePublished by a median 14 days, 4 for same-year CVEs. Data and script. (2026-11-09) - [cvelistV5 delta.json and deltaLog.json: Sync CVE Changes](https://firewallsync.com/posts/cvelistv5-delta-json-deltalog-incremental-cve-sync/index.md): cvelistV5's deltaLog.json lists every new and updated CVE record for about 30 days. Read fetchTime, new and updated, dedupe by cveId, re-baseline when stale. (2026-11-08) - [EPSS Scores for KEV CVEs: Why New Entries Score Low](https://firewallsync.com/posts/epss-scores-for-kev-cves-low-after-listing-threshold-audit/index.md): EPSS for KEV CVEs starts low: 49% of entries added in the last 90 days sit below 0.1, and late risers took a median 14 days to cross it. Audit script inside. (2026-11-07) - [EPSS v5: How Scores Shifted and What to Re-baseline](https://firewallsync.com/posts/epss-v5-score-shift-model-version-v2026-06-15/index.md): EPSS v5 went live on June 15, 2026. CVEs at or above 0.1 fell 26% overnight and top-1,000 overlap was 588. Diff data, threshold fixes and a model_version guard. (2026-11-06) - [CSAF VEX product_tree: Resolve Product IDs to SBOM purls](https://firewallsync.com/posts/csaf-vex-product-tree-product-status-purl-sbom-matching/index.md): CSAF VEX product_status lists hold product IDs, not purls. Walk product_tree branches and relationships to purls, then join to your SBOM. Tested Python inside. (2026-11-05) - [WordPress CVE-2026-119977: Patch the Upgrade Race RCE](https://firewallsync.com/posts/wordpress-cve-2026-119977-upgrade-race-rce-kev/index.md): CVE-2026-119977 lets attackers hijack WordPress 4.7-7.1.3 core updates. Block /wp-content/upgrade/, then update to 7.1.4 or your branch fix. KEV due 6 Nov. (2026-11-04) - [CVE ADP Containers: CISA-ADP, CVE Program and Supplier ADPs](https://firewallsync.com/posts/cve-adp-containers-cisa-adp-cve-program-supplier-sadp/index.md): CVE ADP containers explained: what CISA-ADP, the CVE Program Container and supplier ADPs (redhat-SADP, siemens-SADP) add to a CVE record, and how to merge them. (2026-11-03) - [Vulnerability Prioritization Workflow: CVE Record to Ticket](https://firewallsync.com/posts/vulnerability-prioritization-workflow-cve-record-to-patch-ticket/index.md): Vulnerability prioritization workflow from CVE record to patch ticket: record state, affected check, VEX, KEV, CISA SSVC, EPSS, plus a tested Python script. (2026-11-02) - [VMware ESX CVE-2026-41709: Patch the Logging Gap Now](https://firewallsync.com/posts/vmware-esx-cve-2026-41709-insufficient-logging-kev/index.md): CVE-2026-41709 lets an ESX admin act unlogged. Patch to ESXi80U3j-25429389, 9.0.2.0100 or 9.1.0.0 builds and forward host logs off-box. KEV due 11 Nov. (2026-11-01) - [Ivanti CVE-2026-111357 and CVE-2026-118527: What to Do](https://firewallsync.com/posts/ivanti-connect-secure-cve-2026-111357-cve-2026-118527-kev/index.md): Ivanti CVE-2026-111357 and CVE-2026-118527 are in CISA KEV and chain with CVE-2026-104935. Fixed versions, the gaps in the record, and how to triage your VPN. (2026-10-31) - [GitLab CVE-2026-97229: Patch the Regex RCE, Then Hunt](https://firewallsync.com/posts/gitlab-cve-2026-97229-ci-regex-rce-patch-and-hunt/index.md): GitLab CVE-2026-97229 is exploited and in CISA KEV. Upgrade to 19.5.1, 19.4.3, 19.3.6 or 19.2.9 to close it and its sibling regex RCE CVEs, then hunt. (2026-10-30) - [Magento CVE-2026-48356 (PolyShell): Patch and Hunt](https://firewallsync.com/posts/magento-cve-2026-48356-polyshell-patch-and-hunt/index.md): Magento CVE-2026-48356 (PolyShell) is on CISA's KEV list. Install the 2026-jul builds, block pub/media/custom_options, then hunt CMS blocks and uploads. (2026-10-29) - [Brotli CVE-2026-111497: Find and Patch Every Copy](https://firewallsync.com/posts/brotli-cve-2026-111497-find-and-patch-every-copy/index.md): Brotli CVE-2026-111497: fixed versions for libbrotli, Node.js, Python and Go, why version strings mislead, and a tested script that checks source for the fix. (2026-10-28) - [PHP2Shell CVE-2026-109618 and -109619: Patch, Then Hunt](https://firewallsync.com/posts/php2shell-cve-2026-109618-cve-2026-109619-patch-and-hunt/index.md): PHP2Shell (CVE-2026-109618, CVE-2026-109619) gives unauthenticated RCE on PHP web servers. Fixed: 8.2.35, 8.3.36, 8.4.27, 8.5.12. Stopgaps and hunt steps. (2026-10-27) - [PAN-OS CVE-2026-0322: Patch the Management Interface RCE](https://firewallsync.com/posts/pan-os-cve-2026-0322-management-interface-rce-patch-and-hunt/index.md): CVE-2026-0322 gives an authenticated attacker root on PAN-OS firewalls and Panorama via the management interface. Fixed releases, exposure checks, what to hunt. (2026-10-26) - [VeloCloud Orchestrator CVE-2026-114625: Patch and Hunt](https://firewallsync.com/posts/velocloud-orchestrator-cve-2026-114625-patch-and-hunt/index.md): CVE-2026-114625 lets any logged-in VeloCloud Orchestrator user act as superuser. Fixed in 5.2.3.18, 6.1.3.10 and 6.4.2.12. What to patch and what to hunt. (2026-10-25) - [Collabora CODE CVE-2026-110447: Patch Nextcloud, Then Hunt](https://firewallsync.com/posts/collabora-code-cve-2026-110447-nextcloud-patch-and-hunt/index.md): CVE-2026-110447 lets unauthenticated attackers run commands through Nextcloud's built-in Collabora CODE app before 26.4.303. Who is affected and what to hunt. (2026-10-24) - [Atlassian CVE-2026-21589 File Read: Patch and Hunt](https://firewallsync.com/posts/atlassian-cve-2026-21589-data-center-file-read-patch-and-hunt/index.md): CVE-2026-21589 lets unauthenticated attackers read web-root files in Jira, Confluence, Bitbucket and other Atlassian Data Center apps. Fixes and hunting steps. (2026-10-23) - [BeyondTrust CVE-2026-102764: Patch, Then Hunt for SAWFLY](https://firewallsync.com/posts/beyondtrust-remote-support-cve-2026-102764-patch-and-hunt/index.md): BeyondTrust Remote Support CVE-2026-102764 was exploited as a zero-day. Patch self-hosted appliances with BT26-05-RS, then hunt for SAWFLY and BARECLAW. (2026-10-22) - [Plex Media Server CVE-2026-96656 Chain: Patch and Hunt](https://firewallsync.com/posts/plex-media-server-cve-2026-96656-exploited-chain-patch-and-hunt/index.md): Plex Media Server CVE-2026-96652, -96654, -96655 and -96656 are exploited in the wild. Fixed in 1.43.3.10861. Deadlines, chain details and what to check. (2026-10-22) - [SSVC Deployer Model Explained: How Exploitation, Exposure, Automatable and Human Impact Set Patch Priority](https://firewallsync.com/posts/ssvc-deployer-patch-priority-model-explained-exploitation-exposure-automatable-and-human-impact/index.md): SSVC deployer patch-priority model explained: the four decision points (Exploitation, System Exposure, Automatable, Human Impact), the Defer, Scheduled, Out-of-cycle and Immediate outcomes, the full 72-row decision table, worked examples with real CVE records, and a documentation inconsistency in Human Impact. (2026-10-18) - [How to Read a CVSS v4.0 Vector String, Metric by Metric, with Real CVE Records](https://firewallsync.com/posts/how-to-read-a-cvss-v4-0-vector-string-metric-by-metric-with-real-cve-records/index.md): CVSS v4.0 vector string explained: Base, Threat, Environmental and Supplemental metrics, the CVSS-B, CVSS-BT, CVSS-BE and CVSS-BTE names, default values, strict ordering, and worked examples from real CVE records with scores recomputed and checked. (2026-10-17) - [CVE Record States: Published, Rejected and Disputed, and What Each Means for Vulnerability Triage](https://firewallsync.com/posts/cve-record-states-published-rejected-and-disputed-what-each-means-for-vulnerability-triage/index.md): CVE record states explained: what PUBLISHED and REJECTED mean, what the disputed, unsupported-when-assigned and exclusively-hosted-service tags promise, real examples from CVE Services, and how to handle each in vulnerability triage. (2026-10-16) - [EPSS Data Feed Columns: epss vs percentile, Joined to Scans](https://firewallsync.com/posts/epss-data-feed-columns-percentile-vs-probability-and-how-to-join-it-to-a-scanner-export/index.md): EPSS daily CSV columns: cve, epss (30-day exploitation probability) and percentile. What each means, model-version breaks and a tested Python scanner join. (2026-10-16) - [CISA KEV JSON Feed: Every Field and a Scanner Match Script](https://firewallsync.com/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/index.md): The CISA KEV JSON feed has 12 fields per entry. What dueDate, knownRansomwareCampaignUse and forensicTriage mean, plus a tested Python join to a scanner CSV. (2026-10-15) - [CISA Vulnrichment SSVC: Read CVE Record Values with jq](https://firewallsync.com/posts/cisa-vulnrichment-how-to-read-ssvc-values-in-a-cve-record-and-turn-them-into-a-patch-decision/index.md): CISA Vulnrichment adds Exploitation, Automatable and Technical Impact to CVE records. Pull them with curl and jq, then map them to Track, Track*, Attend or Act. (2026-10-14) - [CISA BOD 26-04 Explained: KEV Deadlines, Forensic Triage and What Private Teams Can Borrow](https://firewallsync.com/posts/cisa-bod-26-04-explained-kev-deadlines-forensic-triage-and-what-private-teams-can-borrow/index.md): CISA BOD 26-04 explained: who it applies to, how the four risk inputs set remediation timelines, the forensic triage requirement, the phase dates, and which practices non-federal teams can borrow. (2026-10-12) - [SPF, DKIM and DMARC: What Each Record Does and What Gmail and Outlook Require](https://firewallsync.com/posts/spf-dkim-and-dmarc-what-each-record-does-and-what-gmail-and-outlook-require/index.md): What SPF, DKIM and DMARC each verify, how DMARC alignment works, the Gmail and Outlook.com bulk sender requirements, and the DMARC update in RFC 9989. (2026-10-10) - [Open Source vs Commercial SIEM: What Actually Changes at Small Scale](https://firewallsync.com/posts/open-source-vs-commercial-siem-what-actually-changes-at-small-scale/index.md): Open source vs commercial SIEM for small teams: what genuinely differs beyond license cost, and where each option's real hidden cost actually shows up. (2026-10-09) - [CVSS vs EPSS vs KEV: Which Signal Should Decide What You Patch First?](https://firewallsync.com/posts/cvss-vs-epss-vs-kev-which-signal-should-decide-what-you-patch-first/index.md): CVSS vs EPSS vs KEV explained: what each score measures, where each fails, and a patch prioritization order tested against seven flaws exploited in late 2026. (2026-10-07) - [NetScaler CVE-2026-88779: Exploited SAML Flaw Needs Newer Builds Than Last Week's Zero-Day Fixes](https://firewallsync.com/posts/netscaler-cve-2026-88779-saml-denial-of-service-exploited-patched-last-weeks-zero-days/index.md): CVE-2026-88779 in Citrix NetScaler ADC and Gateway: which SAML configurations are affected, the fixed builds (14.1-73.41, 13.1-64.28), what is confirmed about exploitation, and what to check. (2026-10-06) - [Cisco Catalyst SD-WAN Manager CVE-2026-76504: Fixed Releases and Log Checks](https://firewallsync.com/posts/cisco-catalyst-sd-wan-manager-cve-2026-76504-authentication-bypass-fixed-releases-and-log-checks/index.md): CVE-2026-76504 in Cisco Catalyst SD-WAN Manager: which releases are fixed, what the Live Protect shield does and does not do, and the log entries Cisco says to review. (2026-10-05) - [Zammad Zero-Days CVE-2026-102489 and CVE-2026-102490: What Is Fixed and What Is Not](https://firewallsync.com/posts/zammad-zero-days-cve-2026-102489-and-cve-2026-102490-what-is-fixed-and-what-is-not/index.md): CVE-2026-102489 and CVE-2026-102490 in the Zammad helpdesk: affected versions, what Zammad and DIVD each say, the unresolved root-escalation flaw, and what to do now. (2026-10-05) - [FortiMail CVE-2026-104286: Affected Builds, IBE Workaround](https://firewallsync.com/posts/fortimail-zero-day-cve-2026-104286-no-patch-yet-what-to-do/index.md): FortiMail CVE-2026-104286 (FG-IR-26-175) affects the 7.2, 7.4, 7.6 and 8.0 branches: affected builds, the disable-IBE workaround, log patterns and IPs to hunt. (2026-10-04) - [Citrix NetScaler Zero-Days (CVE-2026-88771, CVE-2026-88772): Patch, Then Hunt](https://firewallsync.com/posts/citrix-netscaler-zero-days-cve-2026-88771-cve-2026-88772-patch-and-hunt/index.md): CVE-2026-88771 and CVE-2026-88772 in Citrix NetScaler ADC and Gateway: affected and fixed builds, exploitation timeline, hunting commands and what to rotate. (2026-10-03) - [Security Champions Programs That Don't Fizzle Out](https://firewallsync.com/posts/security-champions-programs-that-dont-fizzle-out/index.md): Security champions programs usually fail within two quarters for the same predictable reasons. What to structure differently from the start. (2026-10-02) - [Logging for Incidents, Not for Dashboards](https://firewallsync.com/posts/logging-for-incidents-not-for-dashboards/index.md): Security logging best practices for incident response differ from logging for dashboards. What to capture so you can actually reconstruct an incident. (2026-09-30) - [The Tabletop Exercise Gap: Testing Incident Response for Real](https://firewallsync.com/posts/the-tabletop-exercise-gap-testing-incident-response-for-real/index.md): Most incident response tabletop exercises test whether people know the plan, not whether the plan survives contact with a real incident. Here's the fix. (2026-09-27) - [Alert Fatigue Is a Security Metric, Not a Morale Problem](https://firewallsync.com/posts/alert-fatigue-is-a-security-metric-not-a-morale-problem/index.md): Alert fatigue in security operations isn't a staffing problem — it's a signal your detection tuning has failed. Here's how to measure and fix it. (2026-09-26) - [Why Your Incident Postmortems Aren't Preventing Repeats](https://firewallsync.com/posts/why-your-incident-postmortems-arent-preventing-repeats/index.md): Why blameless postmortems often fail to prevent repeat incidents, and how to make action items stick so the same failure does not happen twice. (2026-08-12) ## Privacy & Third-Party Risk Data minimization, PII, GDPR and the SaaS vendors and OAuth apps that can reach your data. - [What Is PII, and Why Classification Is Harder Than It Sounds](https://firewallsync.com/posts/what-is-pii-and-why-classification-is-harder-than-it-sounds/index.md): What actually counts as PII, why classification is genuinely harder than checking a list of field names, and a practical approach to identifying it across real systems. (2026-10-07) - [Data Minimization: The Privacy Principle Most Teams Skip](https://firewallsync.com/posts/data-minimization-the-privacy-principle-most-teams-skip/index.md): Data minimization explained: why collecting more than you need feels harmless upfront but creates compounding security and compliance costs, and how to actually practice it. (2026-10-06) - [What GDPR Actually Requires: A Plain-English Breakdown for Engineering Teams](https://firewallsync.com/posts/what-gdpr-actually-requires-a-plain-english-breakdown-for-engineering-teams/index.md): What GDPR actually requires in practical terms for engineering teams: data minimization, the 72-hour breach rule, DPIAs, and what's genuinely an engineering decision versus a legal one. (2026-10-05) - [Vetting Third-Party SaaS Tools Before They Touch Your Data](https://firewallsync.com/posts/vetting-third-party-saas-tools-before-they-touch-your-data/index.md): Third-party SaaS risk assessment usually stops at a vendor questionnaire. A more useful vetting process focused on what actually predicts incidents. (2026-10-04) ## Fundamentals Plain-English explanations of the core ideas behind security decisions: encryption, the CIA triad, zero-days and more. - [Encryption at Rest vs Encryption in Transit: What Each Actually Protects Against](https://firewallsync.com/posts/encryption-at-rest-vs-encryption-in-transit-what-each-actually-protects-against/index.md): Encryption at rest vs encryption in transit: what each actually protects against, why compliance checklists treating them as one item miss a real gap, and where the boundary between them sits. (2026-10-04) - [What Is a Zero-Day Vulnerability, and How Should You Actually Respond to One?](https://firewallsync.com/posts/what-is-a-zero-day-vulnerability-and-how-should-you-actually-respond-to-one/index.md): What a zero-day vulnerability actually is, how it differs from a regular unpatched CVE, and what a realistic, prioritized response looks like when one affects you. (2026-10-03) - [Symmetric vs Asymmetric Encryption: When to Use Each](https://firewallsync.com/posts/symmetric-vs-asymmetric-encryption-when-to-use-each/index.md): Symmetric vs asymmetric encryption explained: how each actually works, why they're almost always used together in practice, and where each one fits. (2026-10-02) - [What Is the CIA Triad, and Why It Still Shapes Security Decisions](https://firewallsync.com/posts/what-is-the-cia-triad-and-why-it-still-shapes-security-decisions/index.md): The CIA triad explained: what confidentiality, integrity, and availability actually mean in practice, and why most real security decisions trade them off against each other. (2026-10-01) ## Optional - [Write for Us](https://firewallsync.com/write-for-us/): Pitch FirewallSync: practical, sourced security writing from engineers and practitioners on AppSec, identity, cloud, security operations and AI security. What we publish and how to pitch. - [Advertise / Guest Post](https://firewallsync.com/advertise/): How to inquire about a guest contribution placement on FirewallSync. - [Disclaimer](https://firewallsync.com/disclaimer/): FirewallSync articles are general information, not professional security, legal or compliance advice. - [Privacy](https://firewallsync.com/privacy/): What information FirewallSync collects when you visit the site, and what we do with it. - [Terms of use](https://firewallsync.com/terms/): The terms that apply when you read, quote or link to FirewallSync. - [Contact](https://firewallsync.com/contact/): How to reach the FirewallSync team for pitches, corrections and advertising.