FirewallSync covers the parts of cybersecurity that change how engineering teams work day to day: access control, application and API security, cloud identity, incident response, and the new risks that come with AI agents and LLM applications. We write for the people who have to implement security, not just the people auditing it.
What we cover
- AI Security: prompt injection, MCP servers, AI agents and LLM data leakage.
- AppSec & APIs: APIs, webhooks, secrets and the software supply chain.
- Identity & Access: authentication, MFA, passkeys and least privilege.
- Cloud Security: cloud IAM, workload identity and zero trust.
- Security Operations: incident response, logging, alerting and backups.
- Privacy & Third-Party Risk: data minimization, GDPR and SaaS vendor risk.
- Fundamentals: plain-English explanations of core security ideas.
How we write
Every article starts with the problem a team actually runs into, then gives a concrete fix: a rollout order, a checklist, a comparison. We prefer field-tested advice over vendor feature lists, and we say when a recommendation depends on your team’s size or risk tolerance. The details are in our editorial policy.
Who writes it
Articles carry the name of their writer. Our writers:
Craig Leslie
Researcher and writer
Craig Leslie researches and writes about identity, security operations and AI security for FirewallSync. He checks each technical claim against its original source and says when advice depends on a team's size or risk tolerance.
John Marshall
Researcher and writer
John Marshall researches and writes about application, API and cloud security for FirewallSync. He works from standards, vendor documentation and government advisories, and lists his sources at the end of every article.
Pieces without a named writer appear under FirewallSync Editorial. We also publish guest contributions from practitioners; see Write for Us.
Money and independence
Sponsored content, if we publish any, is labeled clearly at the top of the article. See our advertising page and editorial policy.
Get in touch
Questions, tips and error reports are welcome. See the contact page.