# Web Cookie Security Auditor (`quanmatrix/web-cookie-security-auditor`) Actor

Audit Set-Cookie headers on public websites for Secure, HttpOnly, SameSite, scope and session-cookie hygiene with one structured result per URL.

- **URL**: https://apify.com/quanmatrix/web-cookie-security-auditor.md
- **Developed by:** [Rafael Barreto Haddad](https://apify.com/quanmatrix) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.94 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Web Cookie Security Auditor

Audit Set-Cookie headers on public websites for Secure, HttpOnly, SameSite, scope and session-cookie hygiene with one structured result per URL.

### Why use this Actor

Web teams need recurring evidence that authentication and state cookies remain hardened across application, CDN and framework changes.

### Key features

- Buyer-native inputs aligned to **cookie security**.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.

### Quick start

Start with this working example and replace the target values with your own:

```json
{
  "urls": [
    "https://example.com"
  ]
}
```

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

### Input

- `urls` — URLs: Configure URLs for this Actor run.
- `previousSnapshots` — Previous cookie snapshots: Configure Previous cookie snapshots for this Actor run.
- `failRunOnRisk` — Fail on cookie security risk: Configure Fail on cookie security risk for this Actor run.
- `maxUrls` — Maximum URLs: Configure Maximum URLs for this Actor run.
- `concurrency` — Concurrency: Maximum URLs audited in parallel.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

### Output

The Dataset exposes predictable machine-readable output. Representative fields include `dataset`.

### Pricing

This Actor uses Pay Per Event. The current factory base price is **$0.001200 per result event**. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

### Use cases

- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.

### Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

### Limitations

- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

### Detailed documentation

### Detailed documentation

Audit public Set-Cookie behavior for browser hardening, release QA, and recurring configuration regressions.

### Why use this Actor

Cookie behavior changes when application frameworks, reverse proxies, CDNs, authentication systems, and consent layers change. A single missing Secure or HttpOnly flag can matter more than a long generic security report, while modern browser attributes such as SameSite, cookie prefixes, and Partitioned cookies introduce additional failure modes. This Actor converts observable Set-Cookie headers into per-cookie evidence, an aggregate security score, and a reusable snapshot that can be compared across releases.

### Key features

- Evaluates Secure, HttpOnly, and SameSite on every observed Set-Cookie header.
- Detects SameSite=None without Secure.
- Validates `__Secure-` and `__Host-` prefix requirements.
- Detects Partitioned/CHIPS cookies and flags insecure combinations.
- Reports Domain, Path, Max-Age, and very long-lived persistence risks.
- Produces per-cookie issue lists instead of only page-level booleans.
- Generates a normalized cookie snapshot and fingerprint.
- Compares optional previous snapshots and identifies cookie-set drift.
- Supports a fail-after-evidence security gate for automated QA.

### Input

Provide `urls`. Add `previousSnapshots` to compare current public cookie configuration with an earlier run. Set `failRunOnRisk` for CI/CD or monitoring workflows that should fail after evidence is stored. `maxUrls` limits batch size.

### Output

Each URL returns HTTP status, aggregate score, cookie count, high-risk count, normalized per-cookie findings, fingerprint, snapshot-change status, removed-cookie names, regression state, issue codes, and an `agentAction`.

### Example

```json
{
  "urls": ["https://example.com"],
  "previousSnapshots": {},
  "failRunOnRisk": false,
  "maxUrls": 100
}
```

### Use cases

- Authentication-cookie release QA.
- Framework or CDN migration validation.
- Scheduled security posture monitoring.
- Privacy engineering reviews.
- Agency client audits.
- CI regression gates for public sessions and state cookies.

### Pricing

Billing is pay per audited URL result. The Actor does not require a commercial security scanner, browser farm, or AI service.

### Limitations

The Actor observes server-delivered Set-Cookie headers from public unauthenticated requests. JavaScript-created cookies, authenticated-only cookies, browser storage APIs, and consent behavior requiring interaction are outside this static HTTP view.

### Privacy and permissions

Analysis focuses on public response headers and cookie attributes. Cookie values are not required for the security findings and no login credentials are requested.

# Changelog

This Actor's version history is a separate document: https://apify.com/quanmatrix/web-cookie-security-auditor/changelog.md

# Actor input Schema

## `urls` (type: `array`):

Configure URLs for this Actor run.

## `previousSnapshots` (type: `object`):

Configure Previous cookie snapshots for this Actor run.

## `failRunOnRisk` (type: `boolean`):

Configure Fail on cookie security risk for this Actor run.

## `maxUrls` (type: `integer`):

Configure Maximum URLs for this Actor run.

## `concurrency` (type: `integer`):

Maximum URLs audited in parallel.

## `mcpConnectors` (type: `array`):

Optional MCP connectors authorized in your Apify account. Use them to send or write this Actor result to tools such as Slack, Notion, GitHub, Sentry, Supabase, or another compatible MCP service.

## `mcpToolName` (type: `string`):

Optional exact MCP tool name. Leave blank to let the selected MCP action preset discover a compatible tool automatically.

## `mcpToolArguments` (type: `object`):

JSON object passed to the selected MCP tool. String values may use {{actor_title}}, {{result_summary}}, or {{result_json}} placeholders.

## `mcpFailOnError` (type: `boolean`):

When enabled, an MCP delivery error fails the Actor run. Disabled by default so data extraction and intelligence results remain available even if the external destination is unavailable.

## `mcpActionPreset` (type: `string`):

Choose a safe action pattern. AUTO_SAFE_WRITE discovers a compatible non-destructive write tool automatically; use a specific preset for Slack, GitHub, Notion, or database delivery.

## Actor input object example

```json
{
  "urls": [
    "https://example.com"
  ],
  "previousSnapshots": {},
  "failRunOnRisk": false,
  "maxUrls": 100,
  "concurrency": 5,
  "mcpToolName": "",
  "mcpToolArguments": {},
  "mcpFailOnError": false,
  "mcpActionPreset": "AUTO_SAFE_WRITE"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quanmatrix/web-cookie-security-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("quanmatrix/web-cookie-security-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call quanmatrix/web-cookie-security-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quanmatrix/web-cookie-security-auditor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zhveeZc5J6pYG6WAJ/builds/lat7ctUeKKrHW1xyz/openapi.json