Security model

Site-changing access is treated as a serious responsibility.

AgentReadyToday separates scanning from remediation and combines least privilege, encrypted credentials, ownership verification, explicit approval, audit records, and post-change verification.

Operational controls

Guardrails across the full workflow.

These are the controls implemented in the current product. AgentReadyToday does not claim third-party security certifications that it has not earned.

Control 01

Credential separation

Public assessment uses a dedicated AgentReadyToday URL Scanner credential. A customer remediation credential is not required or used for general scanning.

Control 02

Ownership verification

Consequential changes require verified domain control through authorized Cloudflare zone access or the supported DNS and well-known-file verification methods.

Control 03

Least-privilege access

Cloudflare connections are validated against the relevant zone and documented limited permissions. Customers can remove the stored connection and revoke it at Cloudflare.

Control 04

Encrypted provider credentials

Customer Cloudflare tokens are encrypted server-side with authenticated encryption and are not returned through the API after submission.

Control 05

Explicit approval

Supported changes are presented for review. Approval binds to a digest of the proposed operations, so a changed plan requires new approval.

Control 06

Network request controls

URL inputs are validated, private and reserved networks are blocked, DNS and redirects are rechecked, and outbound fetches use response-size and time limits.

Control 07

Audit records

Security-relevant and site-changing actions record the actor, site, target, outcome, request identifier, timestamp, and hashed network information where used.

Control 08

Verification workflow

After an approved supported change, AgentReadyToday verifies the live behavior and starts a new scan so the result can be compared with the baseline.

Security questions

Need clarification about a control or responsible disclosure?

Contact support