Credential separation
Public assessment uses a dedicated AgentReadyToday URL Scanner credential. A customer remediation credential is not required or used for general scanning.
Security model
AgentReadyToday separates scanning from remediation and combines least privilege, encrypted credentials, ownership verification, explicit approval, audit records, and post-change verification.
Operational controls
These are the controls implemented in the current product. AgentReadyToday does not claim third-party security certifications that it has not earned.
Public assessment uses a dedicated AgentReadyToday URL Scanner credential. A customer remediation credential is not required or used for general scanning.
Consequential changes require verified domain control through authorized Cloudflare zone access or the supported DNS and well-known-file verification methods.
Cloudflare connections are validated against the relevant zone and documented limited permissions. Customers can remove the stored connection and revoke it at Cloudflare.
Customer Cloudflare tokens are encrypted server-side with authenticated encryption and are not returned through the API after submission.
Supported changes are presented for review. Approval binds to a digest of the proposed operations, so a changed plan requires new approval.
URL inputs are validated, private and reserved networks are blocked, DNS and redirects are rechecked, and outbound fetches use response-size and time limits.
Security-relevant and site-changing actions record the actor, site, target, outcome, request identifier, timestamp, and hashed network information where used.
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