Skip to main content
Security libraryReviewed

Web application security platforms: find the guide for each part of the stack you already run

Thirty guides to the site builders, content management systems, store platforms, frameworks, runtimes, APIs, sign-in services, databases, hosts, payment webhooks and automation tools a site can be built from.

The stack selector groups them by the part of the stack they cover and, for each one, gives what it helps you check, its asset counted, what to have ready, whether any row acts and where, and what the guide says about a Clever Ops service.

Pages in this section

30 pages

  • .NET Security

    ASP.NET Core provides authentication, authorisation, antiforgery, CORS, Data Protection and configuration for secrets. Which endpoints those features cover, and how each one is set, is decided in your own code and configuration. This guide sets out what Microsoft's documentation says about each control and where its defaults stop, then gives you a control matrix to fill in for your own application, with a worked example in every row. Only one row sends requests: one sign-in and one sign-out by a test account on your own staging copy.

  • API Security

    An API is every route your screens, apps and integrations call, and each route has to refuse the wrong caller on its own. This guide maps the OWASP API Security Top 10 2023 onto one worked example: an OpenAPI endpoint register, checked against the routes your code and logs show, turned into a matrix of roles, records and HTTP methods that covers object access, writable fields, alternate methods, pagination, rate limits, error responses and undocumented endpoints.

  • Auth.js Security

    Auth.js handles sign-in inside your own application, with installation steps for Next.js, Qwik, SvelteKit and Express, and its configuration decides how a session is stored, sealed and ended. This guide follows those decisions in order, with a decision table to fill in for your own application and a local test set that illustrates the JWT and database session strategies side by side.

  • Auth0 Security

    An Auth0 tenant holds the settings that decide who can sign in, through which connections, to which application, and what each token carries. This guide explains the tenant and application settings that matter, what Auth0's documentation says about each, and what Auth0's testing policy allows. It comes with a tenant evidence workbook and a two-application authorisation matrix you run on a development tenant you own.

  • Clerk Security

    Clerk runs sign-in and issues sessions. Your application decides what each signed-in person may read and change. This guide covers the Clerk helpers and settings that sit on that line: middleware and server-side checks, authorised parties, session settings, token claims, metadata, organisation roles, webhooks and the separation of test and live keys, with each fact credited to the page that states it. The worksheet at the end records all of them for your own application.

  • Cloudflare Security

    Cloudflare acts only on traffic that passes through it, and the security features built on its Ruleset Engine run in a fixed order. This guide explains the zone settings that decide both: proxied DNS, the encryption mode to your origin, managed WAF rules, bot controls, rate limits, cache rules, origin authentication and the headers your origin trusts. It comes with a worksheet for your own zone, including owner-run checks of whether your origin answers a request sent around Cloudflare and which visitor address it then believes.

  • Django Security

    Django includes many security features, some always on and some optional, and its deployment checklist includes settings that must be set properly for Django to provide the expected level of security. This guide covers what manage.py check --deploy reports and what it leaves out, the settings and middleware that matter in production, the admin site, uploaded media and raw SQL, and comes with an evidence matrix you fill in for your own project, including two-user permission tests.

  • Drupal Security

    The Drupal Security Team publishes advisories for security problems in Drupal core and in contributed projects covered by its advisory policy. Roles, text formats, web services, file storage and settings.php are set by the people who run each site. This guide shows how to read an SA-CORE or SA-CONTRIB advisory against your installed versions, which release series receive security fixes, and what drupal.org documents for each of those settings, then gives you a register and role permission matrix to fill in for your own site.

  • Express Security

    Express calls itself a routing and middleware web framework with minimal functionality of its own. On this guide's reading, an Express application's security therefore lives in the middleware it adds, the order it adds them in and the defaults it changes. This guide works through each position from the settings to the error handler, the Express advisories to check your versions against, and a middleware-order test matrix with a local lab you can run.

  • Firebase Security Rules

    In a Firebase app the browser reads and writes Firestore, Realtime Database and Cloud Storage directly, and the security rules Firebase evaluates decide what each client request may do. This guide explains how rules behave in each product, where get differs from list and where reads cascade, what App Check adds and what it does not, and comes with a workbook of unauthenticated, signed-in, owner and other-user cases to run on a staging project or in the emulator.

  • GraphQL Security

    Introspection lets a caller ask a GraphQL API for its own schema. Whether yours should answer is a decision about who your clients are, not a finding on its own. This guide sets out what the GraphQL specification and the project's own pages say about introspection, how Apollo Server, GraphQL Yoga and GraphQL.js document switching it off, and a workbook for testing object access, field suggestions, aliases, batching, depth, cost and errors on your own schema.

  • Joomla Security

    What the Joomla project fixes and what is set on your own Joomla site: supported versions and security announcements, extensions and their update sites, user groups and permissions, multi-factor authentication, the API application, configuration.php and backups. It comes with an inventory and access control worksheet you fill in for your own site by reading its settings.

  • Laravel Security

    Laravel ships defences for CSRF, mass assignment and authorisation, and each one depends on settings and code your team controls. This guide sets out what Laravel's own documentation and the Debugbar readme say about debug mode, APP_KEY, Telescope, Horizon, Debugbar, signed URLs, file storage and queues, and gives you an evidence sheet to fill in for your own application.

  • Magento Security

    Adobe announces security fixes for Adobe Commerce and Magento Open Source in its security bulletins, and Adobe's shared responsibility page for its cloud infrastructure says applying patches is the merchant's responsibility. This guide explains how Adobe ships patches, where scripts reach a Magento checkout, and which Admin and API settings matter, then gives you an owner-run register to find your own patch gap.

  • Make.com Security

    A Make scenario can keep copies of what passes through it: in a webhook queue and log, in run history, in incomplete executions and in data stores. This guide maps where Make's own documentation says each copy lives, which team roles can read, replay or edit it, and the settings that change that, with a review sheet for your own account.

  • n8n Security

    What n8n Cloud and self-hosted n8n each leave to you, the settings that decide who can start a workflow and what it can reach, a dated log of n8n security advisories, and a register to fill in one workflow at a time.

  • Netlify Security

    A Netlify project serves one repository as several live deploys, each with its own address, functions and variable values. This guide explains the project and team settings that decide what each deploy context exposes, what Netlify says it secures and what it leaves to you, and what its Acceptable Use Policy says about testing. It comes with a matrix comparing production, Deploy Previews and branch deploys across visibility, environment variables, functions, forms, notifications, headers, redirects and repository visibility, with one synthetic form submission and a review of where your secrets reach.

  • Node.js Security

    A Node.js application takes on flaws from the runtime release it runs on, from the npm packages it installs and from its own code. This guide shows which release lines receive security fixes, what the Node.js threat model leaves to you, and how to triage install scripts, lockfile drift, native modules and provenance changes, with a worksheet and an offline lab you can run.

  • PHP Security

    A PHP application inherits its exposure from the branch it runs on, the php.ini values the web server actually loads, the Composer packages it installs and the way its own code handles output, queries, uploads, sessions, errors and serialised data. This guide sets out what php.net, the PHP project and Composer's documentation say about each, with an evidence checklist you fill in for your own servers and a column that says how to confirm each change.

  • React Security

    Text a component renders is only one of the ways data reaches a React page. Raw HTML, link addresses, style values, refs, third-party scripts, browser storage and build variables each take another route. This guide shows what happens at each one, according to React's documentation, MDN, OWASP, the build tools' documentation and a lab run on React 18.3.1, and gives you a worksheet to trace every flow in your own components.

  • Ruby on Rails Security

    Rails supplies protections against forged requests, SQL injection, mass assignment and Host header attacks, and each one can be switched off, sidestepped or left unconfigured in your own code. This guide explains which Rails release series receive security fixes, how to read a Rails advisory against your Gemfile.lock, what the Rails guides say about credentials, HostAuthorization, strong parameters, SQL fragments, CSRF, CSP and mounted admin dashboards, and gives you a register to fill in for your own application.

  • Shopify Security

    Shopify runs the platform. Who signs in to the admin, which apps are installed and which scopes they were approved for, which theme and pixels are added, where exports go and how a flagged order is handled are set or decided in each store. This guide sets out what Shopify's own terms and documentation say about both, then gives you a worksheet for your own store and a checklist for a synthetic test order placed without a real card.

  • Squarespace Security

    Squarespace runs the hosting and the editor. Who can sign in, what code your pages load and where visitors' details are sent are set inside your own account. This guide reports what Squarespace's own help guides, security page and terms say about them, and comes with a map to fill in: read-only parts on contributors, code and form storage, then an offboarding and code removal checklist that changes the site.

  • Stripe Webhook Security

    How Stripe signs the events it sends, what your handler has to check before it trusts one, and how to cope with stale, repeated and out-of-order deliveries. With a fixture table, an endpoint register to fill in for your own account, and a local lab of invented test-mode events.

  • Supabase RLS

    With the publishable key shipped in your app, row level security decides which rows each request reaches. This guide explains how Supabase RLS policies and grants make that decision, which keys skip it, where views, Storage and database functions follow different rules, and gives you a two-tenant matrix to run on Supabase's local stack or on a staging project of your own that holds only invented data.

  • Vercel Security

    A Vercel project serves the same code at several addresses, each with its own protection, variables and logs. This guide explains the account and deployment settings that decide what each one exposes, what Vercel says is its job and what is yours, and what Vercel's terms say about testing. It comes with a worksheet that compares production, preview and branch deployments, control by control, using only read-only checks.

  • Webflow Security

    Webflow runs the platform and the hosting. This guide covers the parts a site owner sets on top of it: custom code and embeds, the forms that collect visitors' details, and the apps, API tokens, webhooks and people with access. Each statement about Webflow is credited to the Webflow page that makes it, and the inventory at the end lists every script and form on your site, the forms each script shares a page with, and every place each form's data goes.

  • Wix Security

    Wix hosts the site and runs the platform. Many of the settings that decide what a visitor, a member or an installed app can reach are made by you and the people you give access to: collection permissions, member settings, form recipients, apps, custom code and any Velo code a developer added. Each statement about Wix below names the Wix page it comes from. The page comes with an access matrix you fill in from your own account, plus anonymous, member and owner checks run on a duplicate site with invented records.

  • WooCommerce Security

    A WooCommerce store is a WordPress site with a payment chain attached: gateway extensions, the scripts they load at checkout, the addresses that answer their callbacks, the webhooks that carry events in and out, and the order statuses that move stock and send email. This guide maps that chain from WooCommerce's own documentation, then gives you a dependency graph to fill in from your store and a capped staging run of test orders, a coupon, a refund and a cancellation that records how the chain behaves.

  • Zapier Security

    This guide does not hand Zapier a pass or a fail. It sets out what Zapier's documentation says about connected accounts, the data kept in Zap history, webhook URLs, sharing and offboarding, each credited to the article that says it, then gives you a register for reviewing every Zap in your own account.

Stack selector: thirty platform guides in eleven parts of the stack

Find the part of your stack in the first column, then read across: the guide and its address, what it helps you check in its own terms, its asset counted from the page, what to have ready, whether any row sends a request, submits a form or changes something and where that row runs, and what the guide's closing section says about a Clever Ops service. Rows are numbered 1 to 30 and run in the order of the eleven groups, from site builders to automation.

How to use it

Every cell restates its guide no more strongly than the guide does, and the thirty guides are linked under Pages in this section.

30 rows

Stack selector: thirty platform guides in eleven parts of the stack

Part of the stackGuide and addressWhat it helps you checkIts asset, countedHave readyReads only, or also actsWhat the guide says about Clever Ops
Site builder1. Webflow Security, at /web-security/webflowThe layer a site owner sets on top of Webflow's platform and hosting: custom code and embeds, the forms that collect visitors' details, and the apps, API tokens, webhooks and people with access.A text template, the custom-code and form data-flow inventory. Part 1 is a worked example for an invented business and Part 2 the blank form. Parts A to D map people, code, forms and connections, and Part E is a staged removal plan.Your Webflow dashboard and Designer, your published pages as a visitor's browser receives them, and the owner of each connected system to confirm where its data goes. One inventory per site.Parts A to D read. Part E is the only part that changes anything, and it keeps each change off the live domain: in preview, on the staging domain or on a duplicate site, within the limits written there.Describes no Clever Ops service for Webflow, and Clever Ops does not test Webflow's platform. A web application you own that customers or staff sign in to and that the site hands data to, including the route that receives Webflow's webhooks, sits within a scoped web application and API penetration test.
Site builder2. Wix Security, at /web-security/wixThe settings that decide what a visitor, a member or an installed app can reach: collection permissions, member settings, form recipients, apps, custom code and any Velo code a developer added.A table, the app and Velo access matrix: 20 rows by 4 columns, 14 readings of your live site (A1 to A14) and 6 checks on a duplicate site (B1 to B6).Your own account, and the people the matrix names to ask. For B1 to B6, a duplicate site you made, at most two test members, invented records carrying a marker and an inbox you control. One copy per site.A1 to A14 change nothing. B1 to B6 run anonymous, member and owner checks only on the duplicate, cut off from live apps, automations and mailing lists first, in a browser, with no more than three attempts at any single check and no load.Describes no Clever Ops service for Wix sites, and Wix's platform is not something Clever Ops tests. An application of yours with its own sign-in that exchanges data with the site, and not the Wix site, is what a scoped web application and API penetration test covers.
Site builder3. Squarespace Security, at /web-security/squarespaceWho can sign in, what code your pages load and where visitors' details are sent, each set inside your own account, as Squarespace's help guides, security page and terms describe them.A text template, the contributor, code and data map, in four parts: A inventories contributors and code, B maps each form to its storage and the connected services, C lists findings, and D is an offboarding and third-party code removal checklist.Your own account's panels, your published pages viewed logged out in a private window, and each person reading only their own account settings. One map per site.Parts A to C only read. Part D changes the site or the account, one change at a time, with the way back recorded first and no test submission that reaches a real customer, a mailing list or anyone outside the business.An informational guide: Clever Ops does not test Squarespace's platform, and nothing in it describes a Squarespace-specific testing service. A web application you own that customers or staff sign in to and that the site passes data to sits within a scoped web application and API penetration test.
Content management system4. Drupal Security, at /web-security/drupalHow to read a Drupal Security Team advisory for core or a covered contributed project against your installed versions, which release series receive security fixes, and what drupal.org documents for roles, text formats, web services, file storage and settings.php.A text template, the advisory register and role permission matrix, in four parts: core version and support (8 lines), projects, custom code and external libraries (4 lines), a log of 8 drupal.org advisories, and a role permission matrix (10 blocks).Access you already have: the site's screens and reports, drupal.org pages, files and printed command output, and your host or developer to ask. One copy per site and environment.Reads only. No line changes a permission, installs a module, edits settings.php, runs update.php or sends test requests to any site, and each role is read from its Edit role page without signing in as anyone else.Information only: describes no service built around Drupal, and tests nothing in Drupal core or a contributed module. A custom web application run alongside the site, such as a member portal or a booking system, is scoped under the web application penetration test.
Content management system5. Joomla Security, at /web-security/joomlaWhat the Joomla project fixes and what is set on your own site: supported versions and security announcements, extensions and their update sites, user groups and permissions, multi-factor authentication, the API application, configuration.php and backups.A table, the inventory and access control worksheet: 17 rows by 5 columns, 6 inventory rows followed by 11 access control rows.The administrator area, the site's settings, file listings and web server configuration, read by the people who run the site. Fill in the inventory rows first. One copy per site.Reads only. No step saves a form, changes a permission, resets a token, runs an update or opens a backup.For information only: names no Clever Ops service specific to Joomla, and nothing in it is a test of Joomla. A custom web application or API beside the site, such as a customer portal, sits within a scoped web application penetration test.
Store platform6. WooCommerce Security, at /web-security/woocommerceThe payment chain of a WordPress store: gateway extensions, the scripts they load at checkout, the addresses that answer their callbacks, the webhooks that carry events in and out, and the order statuses that move stock and send email.A table, the integration dependency graph and staging evidence log: 25 rows by 5 columns, 14 rows that trace the chain, 9 staging rows and 2 PCI DSS reference rows.A separate spreadsheet per store. For the staging rows, a staging copy of your own store with each gateway in the test or sandbox mode its documentation describes, one invented test customer and an email inbox the business controls.Rows 1 to 14 read the live store and change nothing; row 3 also adds one product to a cart on the staging copy and loads its checkout there. Rows 15 to 23 run in order on the staging copy: at most three checkout submissions, one coupon reuse attempt, one partial refund and one status change, never a real card, one request at a time and no load.Sits inside the Clever Ops WordPress security audit, which covers WooCommerce stores and adds customer accounts, orders and checkout pages to the scope. Its report is not a PCI DSS assessment, and Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.
Store platform7. Magento Security, at /web-security/magentoHow Adobe ships security patches for Adobe Commerce and Magento Open Source and how to find your own patch gap, where scripts get into a checkout, and which Admin and API settings matter.A table, the patch-gap and checkout-script register: 28 rows by 4 columns, 6 patch-gap rows, 8 bulletin rows each with the date it was read, 6 checkout-script rows, 5 access rows and 3 indicator rows.The store owner, an office manager with Admin access and the developer or agency who looks after the code, working through it together. One copy per installation, with a column added for your answers.Each row reads a setting, list, file, log, report, document or Adobe page, asks your host or developer, requests a page or address of your own store, or runs a command that reports versions, patch status or advisories. The Content Security Policy row also uses one guest cart on your staging copy.Describes no Magento-specific Clever Ops service, and Clever Ops does not test Adobe's platform or its cloud infrastructure. Active tests against your own store, treated as an application, belong to a scoped web application and API penetration test, which is not a PCI DSS assessment.
Store platform8. Shopify Security, at /web-security/shopifyWhat Shopify's own terms and documentation say Shopify provides, beside what is set or decided in each store: who signs in, which apps and scopes are approved, theme code and pixels, exports, webhooks, domains and how a flagged order is handled.A table, the shared-responsibility worksheet and test-order checklist: 17 rows by 5 columns, 12 worksheet rows and a 5-row synthetic test order.Your store's admin and the people to ask. For the test order, a dev store you own, invented customer details, an inbox the business controls and a test payment method Shopify documents. One copy per store.Rows 1 to 12 read or ask and change nothing. Rows 13 to 17 run on the dev store, never the live store, with at most three checkout attempts and never a real card.Outside the service: Clever Ops does not test live Shopify storefronts, so there is no Shopify store audit, penetration test or scan, and the guide describes none. Its worksheet is for the store owner, the people who look after the store, or another provider.
Framework9. React Security, at /web-security/reactThe routes other than rendered text by which outside data reaches a React page: raw HTML, link addresses, style values, refs, third-party scripts, browser storage and build variables.A text template, the untrusted-data trace worksheet with sanitisation fixtures: a worksheet in nine sections (0 to 8), a fixtures lab of three files with output copied from a real run, and a part on what the lab does not show.Your own source files, build configuration and the HTML your application serves. One copy per application, or per area of a large one. The lab needs Node.js with the react and react-dom packages installed where its files sit, and downloads nothing.The worksheet only reads. The lab renders invented components with react-dom/server and prints what React wrote; no browser runs and nothing is sent anywhere.Informational: nothing in it describes a test of React itself. Your own React application sits within a scoped web application penetration test, and the guide also names the secure code review and the website security check.
Framework10. Express Security, at /web-security/expressMiddleware order and the defaults to check, position by position from the settings to the error handler, and the Express advisories to check your versions against.A text template, the middleware-order test matrix with a local ordering lab: 12 blocks (A0 to A11), a worked example on the lab's own invented stack, and a lab with 8 fixtures whose files and output were copied from a real run.Your code, lockfile, configuration and logs. For any line that sends a request, a local copy of your application or the lab.Part A reads. A line that sends a request sends it to a local copy of your application or to the lab on 127.0.0.1, never to production; on production a line asks only for what your own browser receives in ordinary use.Informational: describes no test of Express or its middleware projects. Your own Express application sits within a scoped web application penetration test, and Clever Ops also reviews code for custom web applications with read-only access to your repository.
Framework11. Django Security, at /web-security/djangoWhat manage.py check --deploy reports and what it leaves out, the settings and middleware that matter in production, the admin site, uploaded media and raw SQL.A table, the deployment evidence matrix: 15 rows by 5 columns, two of them two-user permission tests.One copy per environment. For the two-user rows, test accounts you create in a staging environment you control.Every step reads a setting, file, list or response. The two-user rows use test accounts on staging and only view pages.Informational: describes no Django-specific service and tests nothing in the framework. Your own Django application is tested inside a scoped web application penetration test, and a secure code review works from read-only access to your repository.
Framework12. Ruby on Rails Security, at /web-security/railsWhich Rails release series receive security fixes, how to read a Rails advisory against your Gemfile.lock, and what the Rails guides say about credentials, HostAuthorization, strong parameters, SQL fragments, CSRF, CSP and mounted admin dashboards.A text template, the release, Gemfile.lock advisory and configuration register, in five parts: releases per environment, an advisory log, 8 configuration check blocks, a two-account authorisation matrix, and a worked example with invented gems and advisory ids.Gemfile.lock, the routes and initializers, and each environment's settings. For the matrix, a staging copy built from the same commit as production, with test accounts and test records only.Parts A to C read and record, and step C.7 also requests each mounted path on your production site once, signed out, and submits nothing. Part D's two-account matrix sends requests on that staging copy only for actions that read, with test accounts and test records; create, update and destroy are filled in from the code.For information: nothing in it tests Ruby on Rails itself. Your own Rails application belongs in a scoped web application penetration test, and the guide also names a secure code review.
Framework13. Laravel Security, at /web-security/laravelWhat Laravel's documentation and the Debugbar readme say about debug mode, APP_KEY, Telescope, Horizon, Debugbar, signed URLs, file storage and queues, beside what each of your environments chose.A table, the configuration evidence sheet: 15 rows by 4 columns, 12 readings and 3 tests.A separate workbook for each environment the internet can reach. For rows 13 to 15, a staging copy you control, test accounts A and B in the same role, a lower-role test account and records those accounts created.Rows 1 to 12 look and write down without changing anything. Rows 13 to 15 test mass assignment, CSRF, and object authorisation and roles on the staging copy.Outside the service: Clever Ops offers no Laravel audit, Laravel penetration test or code review of a Laravel application. The sheet is written for your own developers, or for a provider who does test Laravel applications.
Framework14. .NET Security, at /web-security/dotnetASP.NET Core's controls one at a time: endpoint authorisation and its exceptions, cookie and JWT bearer validation, antiforgery, CORS, model binding, Data Protection keys, secrets and the environment name, with where the documented defaults stop.A table, the ASP.NET Core control matrix: 17 rows by 5 columns, with a worked example from an invented app in every row.Your own repository and hosting settings, filled in by the application's developers and operators. For the cookie row, one test account on a staging copy you control. One copy per environment.Every row reads code, configuration, a log, a listing command's output or a Microsoft page, except the cookie row, which signs one test account in and out once on the staging copy.Informational: describes no .NET-specific service and no testing of the .NET platform or the ASP.NET Core framework. Your own ASP.NET Core application is tested within a scoped web application and API penetration test, and a secure code review reads the repository.
Language and runtime15. Node.js Security, at /web-security/nodejsWhich Node.js release lines receive security fixes, what the Node.js threat model leaves to you, and how to triage install scripts, lockfile drift, native modules and provenance changes.A text template, the runtime and dependency triage worksheet with an offline lab: a six-section worksheet, a worked example for an invented application, and a lab of four files with output copied from a real run.One copy per application, with section 1 filled once for each environment it runs in: developer machine images, CI or build images and production. The lab needs Node.js and npm, with nothing to download.The worksheet only reads, and leaves any change it names for a separate, planned change. The lab installs invented packages from local files and contacts no registry.An informational hardening resource: nothing in it tests Node.js or npm. Your own Node.js application sits within a scoped web application penetration test, and the guide also names a secure code review.
Language and runtime16. PHP Security, at /web-security/phpWhat php.net, the PHP project and Composer's documentation say about the branch you run, the php.ini values the web server actually loads, the Composer packages you install, and six code patterns.A table, the runtime, php.ini and Composer evidence checklist: 25 rows by 5 columns, 14 runtime and configuration rows, 5 Composer rows and 6 code patterns written for the page and not run.Read access to each internet-facing environment's servers and to the repository, with one spreadsheet per environment, and a staging copy for any check that needs a running site.Change nothing while filling it in. The last column says how to confirm a change, on your own staging copy where the check needs a running site.Informational: no PHP-specific service sits behind it. A custom PHP web application falls inside the scoped web application penetration test, except Laravel applications, which are outside the service; for a WordPress site, the WordPress security audit is the closer fit.
API17. API Security, at /web-security/api-securityEvery route your screens, apps and integrations call, mapped against the OWASP API Security Top 10 2023: object access, writable fields, alternate methods, pagination, rate limits, error responses and undocumented endpoints.A table, the endpoint register and role, record and method test matrix: 14 rows (M1 to M14) by 5 columns, worked through an invented equipment-hire API, with a blank-form column for your own.Your own register, built from your specification, code and traffic, with the expected result written before anything is sent. A staging environment you control, with your own test accounts and test records.Sends requests to your own API on that staging environment: one request per check, and for a limit only enough to see one refusal, with no load.In a Clever Ops web application and API penetration test, the API your own application calls is tested as part of the application, routes no screen uses included. Partner or mobile-app access is scoped as a separate surface, and the mobile app itself is not part of the service.
API18. GraphQL Security, at /web-security/graphqlWhether your schema should answer introspection, treated as an exposure decision rather than a finding, and what each resolver allows: object access, field suggestions, aliases, batching, depth, cost and errors.A text template, the schema and resolver review workbook: an introspection decision in 6 items (A1 to A6), 10 test rows (B1 to B10), and every row worked through an invented two-tenant schema on paper.An API you own, an environment you control, and test accounts you created in two test tenants.Rows read your configuration or send individual requests to your own API, one at a time. Only B2 attempts a write, to a test record, and a limit row sends one request just over the limit. Part C was not executed.Informational: nothing in it tests GraphQL, a GraphQL server library or any vendor's platform. The GraphQL API your own front end calls is covered within a scoped web application and API penetration test.
Sign-in provider or library19. Clerk Security, at /web-security/clerkThe Clerk helpers and settings on the line between Clerk's sign-in and your application's own checks: middleware and server-side checks, authorised parties, session settings, token claims, metadata, organisation roles, webhooks and test and live keys.A text template, the Clerk integration worksheet: Part 1 filled in for an invented freight portal, Part 2 the empty form in nine parts (A to I).Your Clerk Dashboard, your hosting provider's list of environment variable names and scopes, and your own code and lockfile. One copy per application that uses Clerk.Reads only. Nothing changes a setting, rotates or reveals a key, signs in as one of your users or sends test requests to Clerk's services or anyone else's system.Clever Ops offers no service for Clerk itself and does not test Clerk's platform. Testing your own running application belongs in a scoped web application and API penetration test, and a secure code review works from the source.
Sign-in provider or library20. Auth0 Security, at /web-security/auth0The tenant and application settings that decide who can sign in, through which connections, to which application, and what each token carries, and what Auth0's testing policy allows.A table, the tenant evidence workbook and authorisation matrix: 23 rows by 5 columns, 16 workbook rows (W1 to W16) and 7 matrix rows (M1 to M7).One copy per tenant. For M1 to M7, a development tenant you own, test users whose email addresses and phone numbers you control, and test records.W1 to W15 read settings, lists, code and logs, and W16 also runs Auth0's readiness check. M1 to M7 run only in the development tenant, each with at most one request to your own API and no load.Not a description of a Clever Ops service for Auth0, and Clever Ops does not test Auth0's platform. For an application that signs users in through Auth0, active testing belongs inside a scoped web application and API penetration test.
Sign-in provider or library21. Auth.js Security, at /web-security/authjsThe session strategy your configuration runs and what it lets you revoke, AUTH_SECRET, cookies, the trusted host and redirects, providers and account linking, and the checks your callbacks and routes make.A text template, the session decision table and local test set, in five parts: a decision tree that settles which session strategy runs, a 13-item record sheet, two lab files, and the output they printed.Your configuration files, the variable names in your hosting provider's settings, the lockfile of the deployed build and counts from your own database. The lab needs Node.js and installs nothing.The record sheet only reads. The lab runs on 127.0.0.1 with invented users and secrets, holds no Auth.js code, and illustrates the two session strategies rather than testing Auth.js.Describes no test of the Auth.js library or of any identity provider's platform. Your own running application sits within a scoped web application and API penetration test, and a secure code review reads the source.
Database and back end22. Supabase RLS, at /web-security/supabaseHow row level security policies and grants decide which rows each request reaches, which keys skip it, and where views, Storage and database functions follow different rules.A table, the two-tenant RLS test matrix: 18 rows by 8 columns, 2 settings rows (P1 and P2) and then rows for a table, a view, Storage buckets and functions called with rpc(), on an invented schema.Supabase's local stack, or a development or staging project of your own that holds only invented data. For the Storage rows, two test users created on staging with email addresses you control.P1 and P2 read. The table, view and function rows run one cell per transaction, ending in rollback. Storage rows S1 to S4 send requests and end with a clean-up. Never a live project.Informational: the Clever Ops methodology puts services run by other businesses, and your host's platform, outside the method. An app made with an AI builder fits the vibe-coded app security check, and a custom application with an API the web application and API penetration test.
Database and back end23. Firebase Security Rules, at /web-security/firebaseHow rules behave in Firestore, Realtime Database and Cloud Storage, where get differs from list and where reads cascade, and what App Check adds and what it does not.A table, the rules test workbook: 21 rows by 7 columns, a set-up row, 19 cases and an emulator regression row, with the expected result for four callers: unauthenticated, signed in owning nothing, owner and other user.One copy per Firebase project and per named Firestore database. A staging project that holds only invented data, and the Local Emulator Suite for list, query and upload cases.Settings rows read the consoles. Simulated requests run in the Rules Playground on staging, without editing or publishing the rules. Row K1 sends requests, if any, only to your own staging copy.Informational: Clever Ops does not test Firebase's platform. An app an AI builder made on Firebase fits the vibe-coded app security check, and a custom application with its own API the web application and API penetration test.
Host and edge24. Vercel Security, at /web-security/vercelThe account and deployment settings that decide what production, preview and branch deployments each expose, what Vercel says is its job and what is yours, and what Vercel's terms say about testing.A table, the deployment exposure worksheet: 13 controls by 6 columns, with production, preview, and branch URLs and staging side by side.Your project and team settings, the Activity Log and your own deployments' URLs. One copy per project.Every step reads a setting, list or log, or sends an ordinary request to one of your own deployment's URLs.Informational: Clever Ops does not test Vercel's platform. Active testing of an application hosted on Vercel sits within a scoped web application and API penetration test.
Host and edge25. Netlify Security, at /web-security/netlifyWhat production, Deploy Previews and branch deploys each expose: visibility, environment variables, functions, forms, notifications, headers, redirects and repository visibility, and what Netlify's Acceptable Use Policy says about testing.A table, the deploy-context exposure matrix: 18 rows by 6 columns, with a secret-exposure review in rows 3 to 5.Your project and team settings. Before row 12, every notification and integration listed in row 11, and each recipient confirmed as yours. One copy per project.Rows 1, 12 and 14 go only to your own site: one page view per kind of address, one synthetic form submission to a preview, and one header request to each of five addresses, with no load. Every other row reads.For information: Netlify's own platform is not something Clever Ops tests. A custom web application or API on Netlify matches the web application and API penetration test, and a brochure or marketing site the website security check.
Host and edge26. Cloudflare Security, at /web-security/cloudflareThe zone settings that decide what Cloudflare acts on and in what order: proxied DNS, the encryption mode to your origin, managed WAF rules, bot controls, rate limits, cache rules, origin authentication and the headers your origin trusts.A table, the zone configuration and rule-order worksheet: 20 rows by 5 columns, including two owner-run checks of your origin.Your Cloudflare dashboard and read access to your own origin server. One copy per zone.Rows 4, 5, 15 and 16 send requests from your own machine, each sent once, to a hostname in your own zone or to your own origin, and row 12 is one page view in your own browser. Every other row reads.Informational: describes no Clever Ops test of Cloudflare's platform. The application behind your zone fits the web application and API penetration test, and a brochure or marketing site the website security check.
Payment events27. Stripe Webhook Security, at /web-security/stripe-webhook-securityHow Stripe signs the events it sends, what your handler has to check before it trusts one, and how to cope with stale, repeated and out-of-order deliveries and a rolled secret.A text template in four parts: a fixture table of 11 kinds of delivery (A1 to A11), an endpoint register of 12 blocks, a 6-line secret-roll plan, and a local lab of invented test-mode events with its captured output.Your Stripe settings and the code and files the register names, with one register per endpoint in each sandbox and in live mode. For the fixtures, a local copy of your handler started with the lab's invented secret and sandbox keys, never live keys.The register reads, and the roll plan is lines to fill in, not a roll. The only requests are six fixtures and the lab's run, sent only to 127.0.0.1 or localhost.For owners checking their own endpoint. In a Clever Ops web application and API penetration test, payment work stays on your application's side, not the provider's platform. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.
Automation28. Zapier Security, at /web-security/zapierWhat Zapier's documentation says about connected accounts, the data kept in Zap history, webhook URLs, sharing and offboarding, each credited to the article that says it, and how to review every Zap in your account.A text template in four parts: a worked example for an invented plumbing business, the blank register with where to look for each entry, an offboarding checklist and a test-record cleanup plan.Your own Zapier account. One register per Zap.Every entry is read in your own account, and nothing asks you to change a setting, reconnect an account, run a test or send a request. The cleanup plan records what each test of a Zap created or sent, using invented customer data; removing a record is a change made in the app that holds it, by that app's owner.Information for reviewing your own account, not a description of a service, and a Clever Ops test leaves Zapier's platform out unless its owner agrees. An application you own that a Zap meets, such as a form handler or an API endpoint, sits within a scoped web application and API penetration test.
Automation29. Make.com Security, at /web-security/makeWhere Make's documentation says a scenario keeps copies of what passes through it (the webhook queue and log, run history, incomplete executions and data stores), which team roles can read, replay or edit them, and the settings that change that.A text template, the scenario review sheet: an 11-section worked example for an invented enquiry scenario, then the blank sheet in the same 11 sections.Your Make organisation, signed in as an Owner or Admin if you can. One sheet per scenario.Reads screens only. Nothing is run, replayed, retried or sent, and where a screen offers an action you look and close it.Informational and describes no Clever Ops service, and Make's platform stays outside a test's scope without Make's agreement. An API of yours that a scenario calls, or webhook handlers that receive Make's requests, can be covered by a web application and API penetration test or a secure code review once in scope.
Automation30. n8n Security, at /web-security/n8nWhat n8n Cloud and self-hosted n8n each leave to you, the settings that decide who can start a workflow and what it can reach, and a dated log of n8n security advisories.A text template in four parts: a workflow register of 8 rows to copy per workflow, a 5-row instance sheet, a log of 10 advisories, and local webhook fixtures, four files and nine requests with their captured output.Your instance's settings and lists. One register for each workflow an outside caller can start, or that holds a credential to a system you care about.Parts A and B read settings, lists and reports, and none records a secret. Part D sends requests only to 127.0.0.1 or localhost.For owners checking their own instance. Testing your application's side of an exchange with an n8n webhook is work for a scoped web application and API penetration test, and n8n Cloud, run by another business, stays out of scope unless its owner agrees.

Part of the stack

Guide and address

  1. Site builder1. Webflow Security, at /web-security/webflow
    What it helps you check
    The layer a site owner sets on top of Webflow's platform and hosting: custom code and embeds, the forms that collect visitors' details, and the apps, API tokens, webhooks and people with access.
    Its asset, counted
    A text template, the custom-code and form data-flow inventory. Part 1 is a worked example for an invented business and Part 2 the blank form. Parts A to D map people, code, forms and connections, and Part E is a staged removal plan.
    Have ready
    Your Webflow dashboard and Designer, your published pages as a visitor's browser receives them, and the owner of each connected system to confirm where its data goes. One inventory per site.
    Reads only, or also acts
    Parts A to D read. Part E is the only part that changes anything, and it keeps each change off the live domain: in preview, on the staging domain or on a duplicate site, within the limits written there.
    What the guide says about Clever Ops
    Describes no Clever Ops service for Webflow, and Clever Ops does not test Webflow's platform. A web application you own that customers or staff sign in to and that the site hands data to, including the route that receives Webflow's webhooks, sits within a scoped web application and API penetration test.

    Open Webflow Security

  2. Site builder2. Wix Security, at /web-security/wix
    What it helps you check
    The settings that decide what a visitor, a member or an installed app can reach: collection permissions, member settings, form recipients, apps, custom code and any Velo code a developer added.
    Its asset, counted
    A table, the app and Velo access matrix: 20 rows by 4 columns, 14 readings of your live site (A1 to A14) and 6 checks on a duplicate site (B1 to B6).
    Have ready
    Your own account, and the people the matrix names to ask. For B1 to B6, a duplicate site you made, at most two test members, invented records carrying a marker and an inbox you control. One copy per site.
    Reads only, or also acts
    A1 to A14 change nothing. B1 to B6 run anonymous, member and owner checks only on the duplicate, cut off from live apps, automations and mailing lists first, in a browser, with no more than three attempts at any single check and no load.
    What the guide says about Clever Ops
    Describes no Clever Ops service for Wix sites, and Wix's platform is not something Clever Ops tests. An application of yours with its own sign-in that exchanges data with the site, and not the Wix site, is what a scoped web application and API penetration test covers.

    Open Wix Security

  3. Site builder3. Squarespace Security, at /web-security/squarespace
    What it helps you check
    Who can sign in, what code your pages load and where visitors' details are sent, each set inside your own account, as Squarespace's help guides, security page and terms describe them.
    Its asset, counted
    A text template, the contributor, code and data map, in four parts: A inventories contributors and code, B maps each form to its storage and the connected services, C lists findings, and D is an offboarding and third-party code removal checklist.
    Have ready
    Your own account's panels, your published pages viewed logged out in a private window, and each person reading only their own account settings. One map per site.
    Reads only, or also acts
    Parts A to C only read. Part D changes the site or the account, one change at a time, with the way back recorded first and no test submission that reaches a real customer, a mailing list or anyone outside the business.
    What the guide says about Clever Ops
    An informational guide: Clever Ops does not test Squarespace's platform, and nothing in it describes a Squarespace-specific testing service. A web application you own that customers or staff sign in to and that the site passes data to sits within a scoped web application and API penetration test.

    Open Squarespace Security

  4. Content management system4. Drupal Security, at /web-security/drupal
    What it helps you check
    How to read a Drupal Security Team advisory for core or a covered contributed project against your installed versions, which release series receive security fixes, and what drupal.org documents for roles, text formats, web services, file storage and settings.php.
    Its asset, counted
    A text template, the advisory register and role permission matrix, in four parts: core version and support (8 lines), projects, custom code and external libraries (4 lines), a log of 8 drupal.org advisories, and a role permission matrix (10 blocks).
    Have ready
    Access you already have: the site's screens and reports, drupal.org pages, files and printed command output, and your host or developer to ask. One copy per site and environment.
    Reads only, or also acts
    Reads only. No line changes a permission, installs a module, edits settings.php, runs update.php or sends test requests to any site, and each role is read from its Edit role page without signing in as anyone else.
    What the guide says about Clever Ops
    Information only: describes no service built around Drupal, and tests nothing in Drupal core or a contributed module. A custom web application run alongside the site, such as a member portal or a booking system, is scoped under the web application penetration test.

    Open Drupal Security

  5. Content management system5. Joomla Security, at /web-security/joomla
    What it helps you check
    What the Joomla project fixes and what is set on your own site: supported versions and security announcements, extensions and their update sites, user groups and permissions, multi-factor authentication, the API application, configuration.php and backups.
    Its asset, counted
    A table, the inventory and access control worksheet: 17 rows by 5 columns, 6 inventory rows followed by 11 access control rows.
    Have ready
    The administrator area, the site's settings, file listings and web server configuration, read by the people who run the site. Fill in the inventory rows first. One copy per site.
    Reads only, or also acts
    Reads only. No step saves a form, changes a permission, resets a token, runs an update or opens a backup.
    What the guide says about Clever Ops
    For information only: names no Clever Ops service specific to Joomla, and nothing in it is a test of Joomla. A custom web application or API beside the site, such as a customer portal, sits within a scoped web application penetration test.

    Open Joomla Security

  6. Store platform6. WooCommerce Security, at /web-security/woocommerce
    What it helps you check
    The payment chain of a WordPress store: gateway extensions, the scripts they load at checkout, the addresses that answer their callbacks, the webhooks that carry events in and out, and the order statuses that move stock and send email.
    Its asset, counted
    A table, the integration dependency graph and staging evidence log: 25 rows by 5 columns, 14 rows that trace the chain, 9 staging rows and 2 PCI DSS reference rows.
    Have ready
    A separate spreadsheet per store. For the staging rows, a staging copy of your own store with each gateway in the test or sandbox mode its documentation describes, one invented test customer and an email inbox the business controls.
    Reads only, or also acts
    Rows 1 to 14 read the live store and change nothing; row 3 also adds one product to a cart on the staging copy and loads its checkout there. Rows 15 to 23 run in order on the staging copy: at most three checkout submissions, one coupon reuse attempt, one partial refund and one status change, never a real card, one request at a time and no load.
    What the guide says about Clever Ops
    Sits inside the Clever Ops WordPress security audit, which covers WooCommerce stores and adds customer accounts, orders and checkout pages to the scope. Its report is not a PCI DSS assessment, and Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.

    Open WooCommerce Security

  7. Store platform7. Magento Security, at /web-security/magento
    What it helps you check
    How Adobe ships security patches for Adobe Commerce and Magento Open Source and how to find your own patch gap, where scripts get into a checkout, and which Admin and API settings matter.
    Its asset, counted
    A table, the patch-gap and checkout-script register: 28 rows by 4 columns, 6 patch-gap rows, 8 bulletin rows each with the date it was read, 6 checkout-script rows, 5 access rows and 3 indicator rows.
    Have ready
    The store owner, an office manager with Admin access and the developer or agency who looks after the code, working through it together. One copy per installation, with a column added for your answers.
    Reads only, or also acts
    Each row reads a setting, list, file, log, report, document or Adobe page, asks your host or developer, requests a page or address of your own store, or runs a command that reports versions, patch status or advisories. The Content Security Policy row also uses one guest cart on your staging copy.
    What the guide says about Clever Ops
    Describes no Magento-specific Clever Ops service, and Clever Ops does not test Adobe's platform or its cloud infrastructure. Active tests against your own store, treated as an application, belong to a scoped web application and API penetration test, which is not a PCI DSS assessment.

    Open Magento Security

  8. Store platform8. Shopify Security, at /web-security/shopify
    What it helps you check
    What Shopify's own terms and documentation say Shopify provides, beside what is set or decided in each store: who signs in, which apps and scopes are approved, theme code and pixels, exports, webhooks, domains and how a flagged order is handled.
    Its asset, counted
    A table, the shared-responsibility worksheet and test-order checklist: 17 rows by 5 columns, 12 worksheet rows and a 5-row synthetic test order.
    Have ready
    Your store's admin and the people to ask. For the test order, a dev store you own, invented customer details, an inbox the business controls and a test payment method Shopify documents. One copy per store.
    Reads only, or also acts
    Rows 1 to 12 read or ask and change nothing. Rows 13 to 17 run on the dev store, never the live store, with at most three checkout attempts and never a real card.
    What the guide says about Clever Ops
    Outside the service: Clever Ops does not test live Shopify storefronts, so there is no Shopify store audit, penetration test or scan, and the guide describes none. Its worksheet is for the store owner, the people who look after the store, or another provider.

    Open Shopify Security

  9. Framework9. React Security, at /web-security/react
    What it helps you check
    The routes other than rendered text by which outside data reaches a React page: raw HTML, link addresses, style values, refs, third-party scripts, browser storage and build variables.
    Its asset, counted
    A text template, the untrusted-data trace worksheet with sanitisation fixtures: a worksheet in nine sections (0 to 8), a fixtures lab of three files with output copied from a real run, and a part on what the lab does not show.
    Have ready
    Your own source files, build configuration and the HTML your application serves. One copy per application, or per area of a large one. The lab needs Node.js with the react and react-dom packages installed where its files sit, and downloads nothing.
    Reads only, or also acts
    The worksheet only reads. The lab renders invented components with react-dom/server and prints what React wrote; no browser runs and nothing is sent anywhere.
    What the guide says about Clever Ops
    Informational: nothing in it describes a test of React itself. Your own React application sits within a scoped web application penetration test, and the guide also names the secure code review and the website security check.

    Open React Security

  10. Framework10. Express Security, at /web-security/express
    What it helps you check
    Middleware order and the defaults to check, position by position from the settings to the error handler, and the Express advisories to check your versions against.
    Its asset, counted
    A text template, the middleware-order test matrix with a local ordering lab: 12 blocks (A0 to A11), a worked example on the lab's own invented stack, and a lab with 8 fixtures whose files and output were copied from a real run.
    Have ready
    Your code, lockfile, configuration and logs. For any line that sends a request, a local copy of your application or the lab.
    Reads only, or also acts
    Part A reads. A line that sends a request sends it to a local copy of your application or to the lab on 127.0.0.1, never to production; on production a line asks only for what your own browser receives in ordinary use.
    What the guide says about Clever Ops
    Informational: describes no test of Express or its middleware projects. Your own Express application sits within a scoped web application penetration test, and Clever Ops also reviews code for custom web applications with read-only access to your repository.

    Open Express Security

  11. Framework11. Django Security, at /web-security/django
    What it helps you check
    What manage.py check --deploy reports and what it leaves out, the settings and middleware that matter in production, the admin site, uploaded media and raw SQL.
    Its asset, counted
    A table, the deployment evidence matrix: 15 rows by 5 columns, two of them two-user permission tests.
    Have ready
    One copy per environment. For the two-user rows, test accounts you create in a staging environment you control.
    Reads only, or also acts
    Every step reads a setting, file, list or response. The two-user rows use test accounts on staging and only view pages.
    What the guide says about Clever Ops
    Informational: describes no Django-specific service and tests nothing in the framework. Your own Django application is tested inside a scoped web application penetration test, and a secure code review works from read-only access to your repository.

    Open Django Security

  12. Framework12. Ruby on Rails Security, at /web-security/rails
    What it helps you check
    Which Rails release series receive security fixes, how to read a Rails advisory against your Gemfile.lock, and what the Rails guides say about credentials, HostAuthorization, strong parameters, SQL fragments, CSRF, CSP and mounted admin dashboards.
    Its asset, counted
    A text template, the release, Gemfile.lock advisory and configuration register, in five parts: releases per environment, an advisory log, 8 configuration check blocks, a two-account authorisation matrix, and a worked example with invented gems and advisory ids.
    Have ready
    Gemfile.lock, the routes and initializers, and each environment's settings. For the matrix, a staging copy built from the same commit as production, with test accounts and test records only.
    Reads only, or also acts
    Parts A to C read and record, and step C.7 also requests each mounted path on your production site once, signed out, and submits nothing. Part D's two-account matrix sends requests on that staging copy only for actions that read, with test accounts and test records; create, update and destroy are filled in from the code.
    What the guide says about Clever Ops
    For information: nothing in it tests Ruby on Rails itself. Your own Rails application belongs in a scoped web application penetration test, and the guide also names a secure code review.

    Open Ruby on Rails Security

  13. Framework13. Laravel Security, at /web-security/laravel
    What it helps you check
    What Laravel's documentation and the Debugbar readme say about debug mode, APP_KEY, Telescope, Horizon, Debugbar, signed URLs, file storage and queues, beside what each of your environments chose.
    Its asset, counted
    A table, the configuration evidence sheet: 15 rows by 4 columns, 12 readings and 3 tests.
    Have ready
    A separate workbook for each environment the internet can reach. For rows 13 to 15, a staging copy you control, test accounts A and B in the same role, a lower-role test account and records those accounts created.
    Reads only, or also acts
    Rows 1 to 12 look and write down without changing anything. Rows 13 to 15 test mass assignment, CSRF, and object authorisation and roles on the staging copy.
    What the guide says about Clever Ops
    Outside the service: Clever Ops offers no Laravel audit, Laravel penetration test or code review of a Laravel application. The sheet is written for your own developers, or for a provider who does test Laravel applications.

    Open Laravel Security

  14. Framework14. .NET Security, at /web-security/dotnet
    What it helps you check
    ASP.NET Core's controls one at a time: endpoint authorisation and its exceptions, cookie and JWT bearer validation, antiforgery, CORS, model binding, Data Protection keys, secrets and the environment name, with where the documented defaults stop.
    Its asset, counted
    A table, the ASP.NET Core control matrix: 17 rows by 5 columns, with a worked example from an invented app in every row.
    Have ready
    Your own repository and hosting settings, filled in by the application's developers and operators. For the cookie row, one test account on a staging copy you control. One copy per environment.
    Reads only, or also acts
    Every row reads code, configuration, a log, a listing command's output or a Microsoft page, except the cookie row, which signs one test account in and out once on the staging copy.
    What the guide says about Clever Ops
    Informational: describes no .NET-specific service and no testing of the .NET platform or the ASP.NET Core framework. Your own ASP.NET Core application is tested within a scoped web application and API penetration test, and a secure code review reads the repository.

    Open .NET Security

  15. Language and runtime15. Node.js Security, at /web-security/nodejs
    What it helps you check
    Which Node.js release lines receive security fixes, what the Node.js threat model leaves to you, and how to triage install scripts, lockfile drift, native modules and provenance changes.
    Its asset, counted
    A text template, the runtime and dependency triage worksheet with an offline lab: a six-section worksheet, a worked example for an invented application, and a lab of four files with output copied from a real run.
    Have ready
    One copy per application, with section 1 filled once for each environment it runs in: developer machine images, CI or build images and production. The lab needs Node.js and npm, with nothing to download.
    Reads only, or also acts
    The worksheet only reads, and leaves any change it names for a separate, planned change. The lab installs invented packages from local files and contacts no registry.
    What the guide says about Clever Ops
    An informational hardening resource: nothing in it tests Node.js or npm. Your own Node.js application sits within a scoped web application penetration test, and the guide also names a secure code review.

    Open Node.js Security

  16. Language and runtime16. PHP Security, at /web-security/php
    What it helps you check
    What php.net, the PHP project and Composer's documentation say about the branch you run, the php.ini values the web server actually loads, the Composer packages you install, and six code patterns.
    Its asset, counted
    A table, the runtime, php.ini and Composer evidence checklist: 25 rows by 5 columns, 14 runtime and configuration rows, 5 Composer rows and 6 code patterns written for the page and not run.
    Have ready
    Read access to each internet-facing environment's servers and to the repository, with one spreadsheet per environment, and a staging copy for any check that needs a running site.
    Reads only, or also acts
    Change nothing while filling it in. The last column says how to confirm a change, on your own staging copy where the check needs a running site.
    What the guide says about Clever Ops
    Informational: no PHP-specific service sits behind it. A custom PHP web application falls inside the scoped web application penetration test, except Laravel applications, which are outside the service; for a WordPress site, the WordPress security audit is the closer fit.

    Open PHP Security

  17. API17. API Security, at /web-security/api-security
    What it helps you check
    Every route your screens, apps and integrations call, mapped against the OWASP API Security Top 10 2023: object access, writable fields, alternate methods, pagination, rate limits, error responses and undocumented endpoints.
    Its asset, counted
    A table, the endpoint register and role, record and method test matrix: 14 rows (M1 to M14) by 5 columns, worked through an invented equipment-hire API, with a blank-form column for your own.
    Have ready
    Your own register, built from your specification, code and traffic, with the expected result written before anything is sent. A staging environment you control, with your own test accounts and test records.
    Reads only, or also acts
    Sends requests to your own API on that staging environment: one request per check, and for a limit only enough to see one refusal, with no load.
    What the guide says about Clever Ops
    In a Clever Ops web application and API penetration test, the API your own application calls is tested as part of the application, routes no screen uses included. Partner or mobile-app access is scoped as a separate surface, and the mobile app itself is not part of the service.

    Open API Security

  18. API18. GraphQL Security, at /web-security/graphql
    What it helps you check
    Whether your schema should answer introspection, treated as an exposure decision rather than a finding, and what each resolver allows: object access, field suggestions, aliases, batching, depth, cost and errors.
    Its asset, counted
    A text template, the schema and resolver review workbook: an introspection decision in 6 items (A1 to A6), 10 test rows (B1 to B10), and every row worked through an invented two-tenant schema on paper.
    Have ready
    An API you own, an environment you control, and test accounts you created in two test tenants.
    Reads only, or also acts
    Rows read your configuration or send individual requests to your own API, one at a time. Only B2 attempts a write, to a test record, and a limit row sends one request just over the limit. Part C was not executed.
    What the guide says about Clever Ops
    Informational: nothing in it tests GraphQL, a GraphQL server library or any vendor's platform. The GraphQL API your own front end calls is covered within a scoped web application and API penetration test.

    Open GraphQL Security

  19. Sign-in provider or library19. Clerk Security, at /web-security/clerk
    What it helps you check
    The Clerk helpers and settings on the line between Clerk's sign-in and your application's own checks: middleware and server-side checks, authorised parties, session settings, token claims, metadata, organisation roles, webhooks and test and live keys.
    Its asset, counted
    A text template, the Clerk integration worksheet: Part 1 filled in for an invented freight portal, Part 2 the empty form in nine parts (A to I).
    Have ready
    Your Clerk Dashboard, your hosting provider's list of environment variable names and scopes, and your own code and lockfile. One copy per application that uses Clerk.
    Reads only, or also acts
    Reads only. Nothing changes a setting, rotates or reveals a key, signs in as one of your users or sends test requests to Clerk's services or anyone else's system.
    What the guide says about Clever Ops
    Clever Ops offers no service for Clerk itself and does not test Clerk's platform. Testing your own running application belongs in a scoped web application and API penetration test, and a secure code review works from the source.

    Open Clerk Security

  20. Sign-in provider or library20. Auth0 Security, at /web-security/auth0
    What it helps you check
    The tenant and application settings that decide who can sign in, through which connections, to which application, and what each token carries, and what Auth0's testing policy allows.
    Its asset, counted
    A table, the tenant evidence workbook and authorisation matrix: 23 rows by 5 columns, 16 workbook rows (W1 to W16) and 7 matrix rows (M1 to M7).
    Have ready
    One copy per tenant. For M1 to M7, a development tenant you own, test users whose email addresses and phone numbers you control, and test records.
    Reads only, or also acts
    W1 to W15 read settings, lists, code and logs, and W16 also runs Auth0's readiness check. M1 to M7 run only in the development tenant, each with at most one request to your own API and no load.
    What the guide says about Clever Ops
    Not a description of a Clever Ops service for Auth0, and Clever Ops does not test Auth0's platform. For an application that signs users in through Auth0, active testing belongs inside a scoped web application and API penetration test.

    Open Auth0 Security

  21. Sign-in provider or library21. Auth.js Security, at /web-security/authjs
    What it helps you check
    The session strategy your configuration runs and what it lets you revoke, AUTH_SECRET, cookies, the trusted host and redirects, providers and account linking, and the checks your callbacks and routes make.
    Its asset, counted
    A text template, the session decision table and local test set, in five parts: a decision tree that settles which session strategy runs, a 13-item record sheet, two lab files, and the output they printed.
    Have ready
    Your configuration files, the variable names in your hosting provider's settings, the lockfile of the deployed build and counts from your own database. The lab needs Node.js and installs nothing.
    Reads only, or also acts
    The record sheet only reads. The lab runs on 127.0.0.1 with invented users and secrets, holds no Auth.js code, and illustrates the two session strategies rather than testing Auth.js.
    What the guide says about Clever Ops
    Describes no test of the Auth.js library or of any identity provider's platform. Your own running application sits within a scoped web application and API penetration test, and a secure code review reads the source.

    Open Auth.js Security

  22. Database and back end22. Supabase RLS, at /web-security/supabase
    What it helps you check
    How row level security policies and grants decide which rows each request reaches, which keys skip it, and where views, Storage and database functions follow different rules.
    Its asset, counted
    A table, the two-tenant RLS test matrix: 18 rows by 8 columns, 2 settings rows (P1 and P2) and then rows for a table, a view, Storage buckets and functions called with rpc(), on an invented schema.
    Have ready
    Supabase's local stack, or a development or staging project of your own that holds only invented data. For the Storage rows, two test users created on staging with email addresses you control.
    Reads only, or also acts
    P1 and P2 read. The table, view and function rows run one cell per transaction, ending in rollback. Storage rows S1 to S4 send requests and end with a clean-up. Never a live project.
    What the guide says about Clever Ops
    Informational: the Clever Ops methodology puts services run by other businesses, and your host's platform, outside the method. An app made with an AI builder fits the vibe-coded app security check, and a custom application with an API the web application and API penetration test.

    Open Supabase RLS

  23. Database and back end23. Firebase Security Rules, at /web-security/firebase
    What it helps you check
    How rules behave in Firestore, Realtime Database and Cloud Storage, where get differs from list and where reads cascade, and what App Check adds and what it does not.
    Its asset, counted
    A table, the rules test workbook: 21 rows by 7 columns, a set-up row, 19 cases and an emulator regression row, with the expected result for four callers: unauthenticated, signed in owning nothing, owner and other user.
    Have ready
    One copy per Firebase project and per named Firestore database. A staging project that holds only invented data, and the Local Emulator Suite for list, query and upload cases.
    Reads only, or also acts
    Settings rows read the consoles. Simulated requests run in the Rules Playground on staging, without editing or publishing the rules. Row K1 sends requests, if any, only to your own staging copy.
    What the guide says about Clever Ops
    Informational: Clever Ops does not test Firebase's platform. An app an AI builder made on Firebase fits the vibe-coded app security check, and a custom application with its own API the web application and API penetration test.

    Open Firebase Security Rules

  24. Host and edge24. Vercel Security, at /web-security/vercel
    What it helps you check
    The account and deployment settings that decide what production, preview and branch deployments each expose, what Vercel says is its job and what is yours, and what Vercel's terms say about testing.
    Its asset, counted
    A table, the deployment exposure worksheet: 13 controls by 6 columns, with production, preview, and branch URLs and staging side by side.
    Have ready
    Your project and team settings, the Activity Log and your own deployments' URLs. One copy per project.
    Reads only, or also acts
    Every step reads a setting, list or log, or sends an ordinary request to one of your own deployment's URLs.
    What the guide says about Clever Ops
    Informational: Clever Ops does not test Vercel's platform. Active testing of an application hosted on Vercel sits within a scoped web application and API penetration test.

    Open Vercel Security

  25. Host and edge25. Netlify Security, at /web-security/netlify
    What it helps you check
    What production, Deploy Previews and branch deploys each expose: visibility, environment variables, functions, forms, notifications, headers, redirects and repository visibility, and what Netlify's Acceptable Use Policy says about testing.
    Its asset, counted
    A table, the deploy-context exposure matrix: 18 rows by 6 columns, with a secret-exposure review in rows 3 to 5.
    Have ready
    Your project and team settings. Before row 12, every notification and integration listed in row 11, and each recipient confirmed as yours. One copy per project.
    Reads only, or also acts
    Rows 1, 12 and 14 go only to your own site: one page view per kind of address, one synthetic form submission to a preview, and one header request to each of five addresses, with no load. Every other row reads.
    What the guide says about Clever Ops
    For information: Netlify's own platform is not something Clever Ops tests. A custom web application or API on Netlify matches the web application and API penetration test, and a brochure or marketing site the website security check.

    Open Netlify Security

  26. Host and edge26. Cloudflare Security, at /web-security/cloudflare
    What it helps you check
    The zone settings that decide what Cloudflare acts on and in what order: proxied DNS, the encryption mode to your origin, managed WAF rules, bot controls, rate limits, cache rules, origin authentication and the headers your origin trusts.
    Its asset, counted
    A table, the zone configuration and rule-order worksheet: 20 rows by 5 columns, including two owner-run checks of your origin.
    Have ready
    Your Cloudflare dashboard and read access to your own origin server. One copy per zone.
    Reads only, or also acts
    Rows 4, 5, 15 and 16 send requests from your own machine, each sent once, to a hostname in your own zone or to your own origin, and row 12 is one page view in your own browser. Every other row reads.
    What the guide says about Clever Ops
    Informational: describes no Clever Ops test of Cloudflare's platform. The application behind your zone fits the web application and API penetration test, and a brochure or marketing site the website security check.

    Open Cloudflare Security

  27. Payment events27. Stripe Webhook Security, at /web-security/stripe-webhook-security
    What it helps you check
    How Stripe signs the events it sends, what your handler has to check before it trusts one, and how to cope with stale, repeated and out-of-order deliveries and a rolled secret.
    Its asset, counted
    A text template in four parts: a fixture table of 11 kinds of delivery (A1 to A11), an endpoint register of 12 blocks, a 6-line secret-roll plan, and a local lab of invented test-mode events with its captured output.
    Have ready
    Your Stripe settings and the code and files the register names, with one register per endpoint in each sandbox and in live mode. For the fixtures, a local copy of your handler started with the lab's invented secret and sandbox keys, never live keys.
    Reads only, or also acts
    The register reads, and the roll plan is lines to fill in, not a roll. The only requests are six fixtures and the lab's run, sent only to 127.0.0.1 or localhost.
    What the guide says about Clever Ops
    For owners checking their own endpoint. In a Clever Ops web application and API penetration test, payment work stays on your application's side, not the provider's platform. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor.

    Open Stripe Webhook Security

  28. Automation28. Zapier Security, at /web-security/zapier
    What it helps you check
    What Zapier's documentation says about connected accounts, the data kept in Zap history, webhook URLs, sharing and offboarding, each credited to the article that says it, and how to review every Zap in your account.
    Its asset, counted
    A text template in four parts: a worked example for an invented plumbing business, the blank register with where to look for each entry, an offboarding checklist and a test-record cleanup plan.
    Have ready
    Your own Zapier account. One register per Zap.
    Reads only, or also acts
    Every entry is read in your own account, and nothing asks you to change a setting, reconnect an account, run a test or send a request. The cleanup plan records what each test of a Zap created or sent, using invented customer data; removing a record is a change made in the app that holds it, by that app's owner.
    What the guide says about Clever Ops
    Information for reviewing your own account, not a description of a service, and a Clever Ops test leaves Zapier's platform out unless its owner agrees. An application you own that a Zap meets, such as a form handler or an API endpoint, sits within a scoped web application and API penetration test.

    Open Zapier Security

  29. Automation29. Make.com Security, at /web-security/make
    What it helps you check
    Where Make's documentation says a scenario keeps copies of what passes through it (the webhook queue and log, run history, incomplete executions and data stores), which team roles can read, replay or edit them, and the settings that change that.
    Its asset, counted
    A text template, the scenario review sheet: an 11-section worked example for an invented enquiry scenario, then the blank sheet in the same 11 sections.
    Have ready
    Your Make organisation, signed in as an Owner or Admin if you can. One sheet per scenario.
    Reads only, or also acts
    Reads screens only. Nothing is run, replayed, retried or sent, and where a screen offers an action you look and close it.
    What the guide says about Clever Ops
    Informational and describes no Clever Ops service, and Make's platform stays outside a test's scope without Make's agreement. An API of yours that a scenario calls, or webhook handlers that receive Make's requests, can be covered by a web application and API penetration test or a secure code review once in scope.

    Open Make.com Security

  30. Automation30. n8n Security, at /web-security/n8n
    What it helps you check
    What n8n Cloud and self-hosted n8n each leave to you, the settings that decide who can start a workflow and what it can reach, and a dated log of n8n security advisories.
    Its asset, counted
    A text template in four parts: a workflow register of 8 rows to copy per workflow, a 5-row instance sheet, a log of 10 advisories, and local webhook fixtures, four files and nine requests with their captured output.
    Have ready
    Your instance's settings and lists. One register for each workflow an outside caller can start, or that holds a credential to a system you care about.
    Reads only, or also acts
    Parts A and B read settings, lists and reports, and none records a secret. Part D sends requests only to 127.0.0.1 or localhost.
    What the guide says about Clever Ops
    For owners checking their own instance. Testing your application's side of an exchange with an n8n webhook is work for a scoped web application and API penetration test, and n8n Cloud, run by another business, stays out of scope unless its owner agrees.

    Open n8n Security

About this library

Web application security platforms: what the thirty guides cover

A business website or application rests on products and projects other people maintain: a site builder or content management system, perhaps a store platform, a framework and the language it runs on, a sign-in service, a database, a host, a payment provider, and automation tools that copy records between them.

This index covers thirty guides in the web security library, each about one of those parts. Every guide works from published sources it credits, and keeps two things apart: what the product, project or standard takes care of, and what is left to the people who build and run the site. Each one comes with an asset you fill in for your own setup.

The guides are written so that whoever looks after a site can check their own configuration, code and accounts. Twenty-four of them describe no Clever Ops service for the product they cover. Three cover code of your own that the web application and API penetration test reaches as part of an application: the API security, GraphQL and Stripe webhook guides.

The WooCommerce guide sits inside the Clever Ops WordPress security audit, and the Shopify and Laravel guides say that their subjects, live Shopify storefronts and Laravel applications, are outside the service.

The last column of the table repeats what each guide's closing section says, so you can see where a guide ends and a test would begin before you open it.

How the stack selector is laid out

The table has one row per guide, thirty in all, numbered 1 to 30, and this page refers to the rows by number.

They are grouped by the part of the stack each guide covers. The groups run from what a site is built with, through what signs people in and where the data is kept, to where the site is served from, how payment events reach it and which automation tools work beside it.

  • Site builder, rows 1 to 3: Webflow, Wix and Squarespace, where the platform runs the hosting and the owner sets what sits on top of it.
  • Content management system, rows 4 and 5: Drupal and Joomla.
  • Store platform, rows 6 to 8: WooCommerce, Magento and Shopify.
  • Framework, rows 9 to 14: React for components in the browser, then Express, Django, Ruby on Rails, Laravel and ASP.NET Core on the server.
  • Language and runtime, rows 15 and 16: Node.js and PHP, with the packages npm and Composer install.
  • API, rows 17 and 18: the API security guide for an application's routes in general, and the GraphQL guide for a schema behind one address.
  • Sign-in provider or library, rows 19 to 21: Clerk and Auth0, services your application signs people in through, and Auth.js, a library installed in your own application.
  • Database and back end, rows 22 and 23: Supabase and Firebase, where the browser can reach the data directly and the policies or rules on the back end decide what each request gets.
  • Host and edge, rows 24 to 26: Vercel and Netlify, which serve several deployments of one project at their own addresses, and Cloudflare, which acts on the traffic that passes through it.
  • Payment events, row 27: your own endpoint that receives Stripe's webhook events.
  • Automation, rows 28 to 30: Zapier, Make and n8n.

Reading across a row

What it helps you check is written in the guide's own terms. Its asset says what kind of thing the asset is and how big, counted from the page as published: rows and columns for a table, parts, blocks or numbered lines for a text template. Have ready comes from the asset's own instructions.

Reads only, or also acts says whether any row sends a request, submits a form or changes something, and where the guide says that row runs. The last column gives what the guide's closing section says about a Clever Ops service, and nothing beyond it.

A cell says what its guide says, no more strongly. The table carries no version numbers, end-of-life dates, advisory ids or plan limits. Those change, so they stay in the guides, each beside the source it came from. The table cannot hold links, so each row gives its guide's address, and all thirty guides are linked under Pages in this section.

Where WooCommerce, React and the Stripe guide sit, and two guides outside the thirty

WooCommerce sits with the store platforms rather than the content management systems because its guide stays with the store. It describes a WooCommerce store as a WordPress site with a payment chain attached, and leaves WordPress roles, login, plugins and admin exposure to the WordPress Security Audit guide. React sits with the frameworks although its guide covers client-side components, and that guide leaves Next.js routing, server components and framework advisories to the Next.js guide.

The Stripe webhook guide has a group of its own because its subject is your endpoint, the route that receives Stripe's events, and not Stripe's platform.

Two platform guides in the library are not among the thirty: Next.js and WordPress. Several rows hand work to them, and both are linked under Related security guides.

From a description of your stack to the first guides to open

Write your stack down in the order of the groups: what the site is built with, what people sign in with, where the data is kept, where the site is served from, how payment events arrive and which automation tools touch it.

Leave a line blank where nothing applies. Every line you fill in points to one row, and the guide in that row is the one written for that part.

Then decide which two or three to open first. This page suggests an order in three steps, built from what the assets record rather than from any view of the products.

  • First, the guide for the part that decides who can reach which record. On a site builder that is the builder's own guide, whose asset covers the people with access and the forms, and on Wix the members and collections too. On Supabase or Firebase it is the database guide, because the browser reaches the data directly and the back end's own policies or rules make the decision. In an application whose server decides, it is the framework guide, the API security guide and the guide for the sign-in provider or library.
  • Second, the guide for where the site is served from. The Vercel and Netlify worksheets set production beside previews and branch deployments, and the Cloudflare worksheet checks whether your origin answers a request sent around Cloudflare. A filled-in copy also gives you the list of addresses that the rest of the work refers to.
  • Third, the guides for whatever copies data out of the application: the automation tool, and the endpoint that receives payment events.

Let the guides' own pointers settle the rest

Several of the guides name a neighbour in this index as the place for the layer next to theirs. The Express guide sends the runtime and npm to the Node.js guide, and the Node.js guide sends middleware order back to Express. The GraphQL guide sends APIs in general and the endpoint register to the API security guide, which names the GraphQL guide for schema and resolver testing and the Stripe webhook guide for a payment provider's calls.

The n8n guide points to the Zapier and Make guides. Following those pointers keeps you from reading two guides for the same layer.

Website security by platform: guides that belong together

Five shapes of site follow, each built from rows in the table.

The order within each is this page's suggestion, taken from where each guide says a neighbouring guide takes over.

A site-builder site: rows 1 to 3, then automation

Open the guide for your builder first. 1 min read

An online store: one of rows 6 to 8, then payments and automation

For WooCommerce, start with row 6. 1 min read

An application with its own sign-in: framework, runtime, API, sign-in and host

A custom application can take a row from each of five groups. 1 min read

An app made with an AI builder: rows 22 and 23

The Supabase and Firebase guides each describe themselves as the technical companion to the vibe coding security guide, which sits outside this index and covers the quick checks for apps an AI builder made, such as sign-up settings, payment flows and keys. 1 min read

An automation-heavy back office: rows 28 to 30, then the API rows

Where tools move records between a website, a CRM, a mailbox and an accounting package, take one guide per tool. 1 min read

What the thirty guides have in common

Set side by side, the guides are built the same way, and knowing the pattern makes each one quicker to use.

  • An asset you fill in for your own setup. Sixteen are tables and fourteen are text templates. Where an asset names the unit to copy it for, keep to it: one per store for WooCommerce, one per tenant for Auth0, one per zone for Cloudflare, one per environment for Django and PHP.
  • Names, never values. Twenty-nine of the assets tell you not to write a secret's value into your copy, and the API security guide asks for tokens and personal details to be redacted from the requests and responses you keep for its matrix.
  • Where a row acts, its guide says where it runs. The places named include a staging copy (WooCommerce, Magento's Content Security Policy row, Laravel, ASP.NET Core and Ruby on Rails), a staging environment you control (Django and the API matrix), Supabase's local stack or a development or staging project that holds only invented data (Supabase), a staging project and the Local Emulator Suite (Firebase), a development tenant (Auth0), a dev store (Shopify), a duplicate site (Wix), a lab on 127.0.0.1 or localhost (n8n, Express, Auth.js and Stripe webhooks), and for the hosts, page views and requests sent once to your own addresses (Vercel, Netlify and Cloudflare).
  • Limits written into those rows: at most three checkout submissions in the WooCommerce staging run and three checkout attempts in the Shopify test order, no more than three attempts at any check on the Wix duplicate, at most one request per row to your API in the Auth0 matrix, and one request per check in the API matrix.
  • A section on what a review of your own setup cannot show. All thirty guides have one, and it is worth reading before a filled-in asset is treated as the whole answer.
  • The vendor's terms before anything active. Thirteen guides give a section of its own to the terms or policies to read before any active test, and the n8n guide has a shorter note on n8n Cloud.

Keep the reading date with your copy

Where a guide gives the day its sources were read, copy that date into your own sheet beside each plan condition, default or support date you rely on, and open the source again before acting on it. The assets that carry such facts in their rows, such as the PHP checklist's support dates, the Magento bulletin rows and the plan conditions in the Vercel, Netlify and Cloudflare worksheets, are the ones most worth that second look.

Where the service pages take over

These guides are for the people who run each setup.

A Clever Ops test is a different piece of work, and its scope comes from the service pages rather than from the guides. Clever Ops tests the parts of a business that customers reach through a browser or an API: marketing websites, WordPress sites and WooCommerce stores, custom web applications and their APIs, apps made with AI builders, and AI chatbots that answer customers or take actions for them.

  • The web application and API penetration test is a signed-in test of a custom application with an API behind it. It covers authentication and sessions, what each role can see and change, whether one customer can reach another customer's records, the API called directly rather than only through the screens, payment and billing flows, file uploads and business rules. Twenty-seven of the closing sections name it for an application of your own.
  • The WordPress security audit follows each role that can log in, and checks the login and password-reset flows, the installed plugin and theme versions and how the admin area is exposed. WooCommerce stores add customer accounts, orders and checkout pages to its scope, which is why row 6 sits inside it.
  • The vibe-coded app security check is for apps made with an AI builder, and concentrates on data exposure, authentication, secrets, payments and abuse, including database rules that let one user read another user's data. The Supabase and Firebase guides name it.
  • The website security check is an external review of what anyone on the internet can see without logging in, and it does not look behind a login. The Cloudflare and Netlify guides name it for a brochure or marketing site.
  • Read-only code access to named areas can be added to a penetration test, and a full secure code review of the repository is scoped as a separate piece of work.

Platforms, products and work outside the service

The methodology puts your host's platform and services run by other businesses outside the method, and keeps those services out of scope unless their owner agrees. That is why a guide can set out a vendor's settings in detail and still say that Clever Ops does not test the vendor's platform. Live Shopify storefronts and Laravel applications, rows 8 and 13, sit outside the service altogether.

Some work needs a different kind of provider. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor, so a PCI DSS scan or assessment goes to a provider that holds that role. Where a tender, panel or contract requires a CREST-accredited provider, Clever Ops is not CREST accredited, so we refer that work to a provider that is.

Denial-of-service, load or volumetric testing is not part of any Clever Ops service, and Clever Ops does not provide managed IT, round-the-clock monitoring or emergency incident response.

Three points apply to every engagement. Your hosting provider's testing policy is checked for each target before any request is sent. If Clever Ops built or hosts the application, the work is a security review rather than an independent test, and the report names who built it and who hosts it.

A report is evidence for a decision someone else makes, such as a customer or an auditor, and it is not a certificate.

A filled-in asset is useful when scoping a test. The closing sections of several guides say how: a completed Vercel or Netlify worksheet already lists the addresses for each environment, a Cloudflare worksheet holds your proxied hostnames and whether the origin answers directly, a Django matrix names the environments, staff accounts, exempt views and raw queries, and the n8n workflow register and the Stripe endpoint register are what to bring to a scoping call.

Frequently asked questions

The row for the part of your stack that decides who can reach which record: the builder's guide for a site-builder site, the Supabase or Firebase guide where the browser reaches the data directly, or the framework, API and sign-in guides where your own server decides. Then the host's guide, then the guides for the tools that copy data out. The section on guides that belong together gives an order for five shapes of site.

Not the platforms themselves. The methodology puts your host's platform and services run by other businesses outside the method, and keeps those services out of scope unless their owner agrees. What Clever Ops tests is your own site or application: the web application and API penetration test covers a custom application and its API, the WordPress security audit covers WordPress sites and WooCommerce stores, and the vibe-coded app security check covers apps made with an AI builder. Live Shopify storefronts and Laravel applications are outside the service.

Rows 4 and 5. The Drupal register reads core and project versions against drupal.org advisories and ends in a role permission matrix, and the Joomla worksheet inventories versions and extensions before its access control rows. Both only read. For a WordPress store, row 6 covers the WooCommerce payment chain, and WordPress itself has a guide in the library outside this index.

Six in this index: React, Express, Django, Ruby on Rails, Laravel and ASP.NET Core, rows 9 to 14. Node.js, beneath Express, and PHP, beneath Laravel, are in rows 15 and 16. Next.js has a guide of its own outside this index. Each framework guide comes with a worksheet, matrix, register or evidence sheet filled in from your own code and configuration.

Only where the guide says so. The WooCommerce staging rows run on a staging copy, the Shopify test order on a dev store, the Wix checks on a duplicate site, the Auth0 matrix in a development tenant and the Supabase matrix on the local stack or a development or staging project with invented data. Where a row does reach your live setup, as in the Vercel, Netlify and Cloudflare worksheets, it is a page view, a request sent once to your own address, or in Netlify's case one synthetic form submission to a preview. The Squarespace offboarding and code removal checklist changes the site or the account, one change at a time with the way back recorded first. Where a guide has a section on its vendor's terms, read it before anything active.

Because they change, and a second copy here would drift away from the guide. Each guide gives them beside the source it read, and some assets put them in the rows themselves, such as the PHP checklist's support dates, the Magento bulletin rows and the plan conditions in the Vercel, Netlify and Cloudflare worksheets. Read them on the guide, and check the source again before relying on one.

This page does not compare or rank them. Each platform guide sets out what that platform's own pages say it handles and what stays with the people who run a site on it, and the WooCommerce, Django, Joomla and Shopify guides each say outright that they give no yes or no answer. The assets record the part that is yours: the settings, code and accounts on your own site.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.