Security Checklists

Step-by-step checklists you can run before launch · from platform-specific lists to full 25-point web app audits.

24 articles

Thumbnail for How to audit a Bubble app for WCAG accessibility
·4 min read

How to audit a Bubble app for WCAG accessibility

Manual review covers key user journeys against WCAG criteria. Bubble's native buttons lack direct controls for adding ARIA labels, which can leave screen readers announcing only a generic button name.

Read article
Thumbnail for Email Security Audit for DMARC Compliance: Sending Sources, Reports and Enforcement
·6 min read

Email Security Audit for DMARC Compliance: Sending Sources, Reports and Enforcement

For a DMARC compliance audit, begin by identifying every system and service that sends email for your domain. Aggregate reports reveal which senders use your domain and where alignment breaks down. Monitoring before enforcement reduces the risk of blocking legitimate email.

Read article
Thumbnail for Why SaaS apps need automated security rescans, not just one-off audits
·4 min read

Why SaaS apps need automated security rescans, not just one-off audits

SaaS apps run in the cloud, on systems you do not own. The provider runs the app and the systems behind it. You still control settings, user access and how your data is handled.

Read article
Thumbnail for How Supabase RLS audit tools find exposed tables and help fix access rules
·6 min read

How Supabase RLS audit tools find exposed tables and help fix access rules

Tables are created with RLS switched off, so rows remain exposed unless protection is turned on. AI builders can create tables faster than they secure them. An app may work in preview while its live API exposes users, orders, messages and documents.

Read article
Thumbnail for What should a service scan of your public endpoints cover?
·7 min read

What should a service scan of your public endpoints cover?

Review public infrastructure, exposed endpoints, and transport configurations against documented operational profiles. Test DNS records, HTTP defensive headers, TLS parameters, and API response bodies systematically across staging and production tiers. Document observed status codes, routing behavior, and certificate details in versioned logs to guide remediation decisions.

Read article
Thumbnail for How do you test a web page with Accessibility Insights for Web?
·6 min read

How do you test a web page with Accessibility Insights for Web?

Inspect web pages using automated checks and interactive keyboard traversal. Record observed markup flags, focus sequences, and color contrast values in your verification log. Compare these observations against your documented team acceptance criteria. Decide whether to release user interface changes or log remediation tasks for unresolved accessibility findings.

Read article
Thumbnail for How to Use an Accessibility Checker for WCAG Compliance
·6 min read

How to Use an Accessibility Checker for WCAG Compliance

Review your site with an automated accessibility checker to surface baseline markup defects. Record every reported element selector, contrast ratio, and missing label. Compare those flags against manual keyboard navigation checks and screen reader flows. Decide remediation priorities based on your release requirements and assign fixes directly to front end engineering tickets.

Read article
Thumbnail for Improving Site Performance: How to Run a 30-Second SEO and Speed Audit
·5 min read

Improving Site Performance: How to Run a 30-Second SEO and Speed Audit

Review target web addresses and verify critical metadata tags before executing diagnostic runs. Record mobile and desktop delivery timings, inspect crawl directives in your robots file, and evaluate script bundle payloads. Compare observed status codes against staging benchmarks to isolate network latency and markup omissions without delaying deployment schedules.

Read article
Thumbnail for How do you manage security test accounts from provisioning to retirement?
·7 min read

How do you manage security test accounts from provisioning to retirement?

A security test account lifecycle checklist is a procedure for managing credentials during audits. It involves provisioning accounts with temporary access, verifying that tokens expire after logout, and ensuring all endpoints require authentication. Proper management includes logging all authorization events and enforcing the automated rotation of API keys to prevent permanent vulnerabilities.

Read article
Thumbnail for How do you build and maintain a third party script approval register?
·5 min read

How do you build and maintain a third party script approval register?

A third party script approval register is a central log used to document and manage external scripts loaded by a web application. It tracks the source, purpose, and ownership of each script to help mitigate security risks like XSS while ensuring integrations align with internal safety and performance requirements.

Read article
Thumbnail for What evidence proves a security finding is fixed after a retest?
·6 min read

What evidence proves a security finding is fixed after a retest?

Security finding retest evidence is the documentation used to verify that a vulnerability has been remediated. It requires dated, signed artifacts such as configuration exports or logs showing a failed exploit attempt. Effective retesting involves linking new evidence to the original finding and performing checks after any software or dependency changes.

Read article
Thumbnail for What evidence should you collect before and after a deployment rollback?
·6 min read

What evidence should you collect before and after a deployment rollback?

A deployment rollback evidence checklist helps teams revert to a stable state while preserving data for analysis. It involves defining clear triggers for failure, testing reversion steps in staging, and establishing communication plans. Capturing logs and environment states before reverting ensures that the root cause can be identified and fixed.

Read article
Thumbnail for The 2026 Web Security Checklist for AI-Built Applications
·9 min read

The 2026 Web Security Checklist for AI-Built Applications

Use this checklist to review database access, secret handling, browser protections, and session security in AI-built applications. Inspect generated code and deployed behavior, and test permitted and denied operations instead of treating a working interface as evidence of security.

Read article
Thumbnail for Modern Security Audit Procedures for Vibe-Coded Applications
·7 min read

Modern Security Audit Procedures for Vibe-Coded Applications

Review an AI-built application through supported automated checks, source review and authorized manual testing. Define the scope, inspect secrets and deployed configuration, test backend permissions with appropriate roles, and document findings, limitations and remediation evidence before relying on a release.

Read article
Thumbnail for The Vibe Coding Security Audit Checklist: Shipping Fast Without Leaking Data
·6 min read

The Vibe Coding Security Audit Checklist: Shipping Fast Without Leaking Data

Vibe coding uses natural language prompts to generate software with AI. Review the resulting application independently: inspect secrets, database access, security headers, and authorization behavior. Combine supported automated findings with code review and targeted tests.

Read article
Thumbnail for The Ultimate Vibe Coding Security Checklist: Ship AI Apps Safely
·10 min read

The Ultimate Vibe Coding Security Checklist: Ship AI Apps Safely

A vibe coding security checklist ensures AI-generated apps are safe for production. Key steps include auditing for exposed API keys, verifying Supabase RLS policies, and validating security headers. Using automated tools like SimplyScan allows developers to maintain the speed of vibe coding without compromising on essential security best practices.

Read article
Thumbnail for Claude Code Security Checklist: Ship Agent-Written Code Safely
·8 min read

Claude Code Security Checklist: Ship Agent-Written Code Safely

Review Claude Code’s effective permissions, isolate sensitive credentials, inspect changes, and treat external content as untrusted input. Tool rules help limit actions, but they are not a substitute for filesystem and network isolation. Check the deployed application as well as the source changes.

Read article
Thumbnail for Broken Access Control Checklist | Find and Fix OWASP A01
·9 min read

Broken Access Control Checklist | Find and Fix OWASP A01

Broken access control occurs when an application permits data access or actions outside its intended rules. Test protected operations on the server or database with the relevant users and roles. Ownership checks, role checks, and database policies should reflect the application’s actual sharing model.

Read article
Thumbnail for How to Check if a Website Is Secure: A 10-Minute Audit
·7 min read

How to Check if a Website Is Secure: A 10-Minute Audit

To check if a website is secure, run five free passive checks: confirm HTTP redirects to a valid HTTPS certificate with TLS 1.2+, verify security headers like CSP and HSTS, scan for exposed .env and .git files, check SPF, DKIM, and DMARC records, and look for a public status page. The whole audit takes about ten minutes.

Read article
Thumbnail for Cursor App Security Checklist: 10 Things to Check Before You Ship
·7 min read

Cursor App Security Checklist: 10 Things to Check Before You Ship

Before shipping a Cursor-built app, review secrets, database access, server-side authorization, input handling, errors, dependencies, browser headers, CORS, and session management. Test the controls relevant to your architecture and investigate deployed findings; a working interface does not establish that private data and actions are protected.

Read article
Thumbnail for Firebase Security Checklist: Protect Your AI-Built App
·11 min read

Firebase Security Checklist: Protect Your AI-Built App

Review Firebase Security Rules, authentication, function authorization, and API-key scope before launch. Test the access each role needs, including anonymous requests. Evaluate App Check separately as an abuse-reduction layer; neither a deadline nor a configuration checklist establishes production safety.

Read article
Thumbnail for React Security Checklist: 10 Vulnerabilities to Fix Before Launch
·6 min read

React Security Checklist: 10 Vulnerabilities to Fix Before Launch

React apps are client-side, making every secret and route guard visible to users. To secure your app before launch, you must move API keys to the server, sanitize HTML with DOMPurify, validate user-provided URLs, and enforce backend authentication for every sensitive request rather than relying on frontend logic.

Read article
Thumbnail for Web App Security Audit Checklist: 25 Checks Before Launch
·11 min read

Web App Security Audit Checklist: 25 Checks Before Launch

This checklist organizes 25 review points across authentication, authorization, data handling, and operations. Adapt it to the application’s requirements and combine supported automated findings with code review and tests. Completing the list does not establish that every vulnerability has been found.

Read article
Thumbnail for Supabase Security Checklist: Protect Your Database in Production
·10 min read

Supabase Security Checklist: Protect Your Database in Production

Supabase’s anon key is intended for client use. Review database privileges, RLS policies, server credentials, authentication settings, and Storage permissions. Configure CORS for the intended browser clients and test protected operations directly.

Read article