Resources
Public materials explain Form Identity Protection, the security model and integration boundaries. Detailed implementation documentation is released to approved customers.
Start here
ColorShield ID Core, Form Identity Protection, Guardian, AuditGuard, Managed Protection and Developer Integration.
Available
SDK, server bootstrap and ColorShield Control Tower, the central authorization and policy engine for protected forms, plus context validation, runtime proof, pre-submit authorization and PERMIT / WARN / BLOCK.
Available
Deterministic Form Identity first; fail-closed BLOCK behavior; clone resistance; telemetry minimization; additive intelligence.
Available
High-level deployment path: public SDK config, same-origin bootstrap, fresh pre-submit authorization and separate business submit.
AvailableDeveloper & deployment
Public summaries below stay commercial-safe. Full SDK, API and deployment materials are released after protected access approval.
Loads on the protected page with public configuration only. Requests trust state, presents Guardian outcomes and prepares fresh pre-submit authorization. It is not the final security authority.
Detailed SDK documentation is provided during approved onboarding.
A same-origin customer-server endpoint adds installation credentials server-side and calls Control Tower. The browser never holds the installation secret.
Bootstrap implementation guidance is released for approved deployments.
Practical go-live path: register authorized domains and protected flows, load the SDK, verify fail-closed submit behavior in BLOCK mode, and confirm protection events in the customer platform.
Full deployment steps are released for approved deployments.
ColorShield can assist installation using temporary, revocable access such as a cPanel API token, limited SFTP/SSH, or a developer-managed path. Runtime protection does not depend on persistent hosting-panel access.
Never provide a cPanel password. Prefer temporary API tokens and revoke access after install.
Each protected flow binds an authorized hostname, exact path and form context. Public SDK values are safe for the browser; installation secrets remain server-side.
Configuration details are provided during approved onboarding.
The ColorShield Control Tower is the server-side security authority for protected forms. It validates authorized domain, path, session, time and form context, issues short-lived runtime proof, evaluates fresh pre-submit authorization, and returns the final PERMIT, WARN or BLOCK decision. It is the central security control plane for protected-form authorization.
Guardian is the trust-state renderer. It shows real SDK / Control Tower outcomes (VERIFIED, WARNING or NOT VERIFIED) and does not create security by itself.
AuditGuard adds warning/block evidence, traceability, event history and authorized notifications around policy outcomes. It complements Core. It does not replace Control Tower authority.
Customer configuration is provided during approved onboarding.
Customer documentation
Detailed technical materials remain gated and are finalized during launch onboarding. A confidentiality agreement may be required before access is granted.
Customer SDK integration guidance for protected application environments.
Provided during approved onboardingCustomer API surfaces for protected deployments.
Released for approved deploymentsDeployment steps for approved production environments.
Released for approved deploymentsConfiguration of authorized domains and protected flows.
Provided during approved onboardingOperational visibility settings for approved deployments.
Released for approved deploymentsEvidence and policy recording configuration for customer environments.
Provided during approved onboardingFAQ
ColorShield ID protects sensitive web-form interactions such as login, registration, checkout, payment, banking / IBAN, personal-data and critical business forms. It validates that the form is operating in an authorized context before protected submission continues. The customer application still owns the business-form payload and downstream processing.
No. ColorShield ID is a live Form Identity and anti-phishing protection platform. ColorShield Control Tower is the central authorization and policy engine for protected forms. Guardian only renders the resulting trust state, and the JavaScript SDK is the integration and runtime client used to request and present that state on the protected page.
Visual badge appearance can be copied, and attackers may reproduce HTML, CSS or JavaScript from a page. Copying those assets alone does not create an authorized ColorShield runtime context. Fresh server-backed validation and pre-submit authorization are still required before a protected submission can continue under ColorShield policy.
No. The browser is never the final ColorShield security authority. ColorShield Control Tower is the central authorization and policy engine for protected forms and owns the ColorShield authorization decision. The JavaScript SDK is an integration client, Guardian only renders trust state, and the customer backend remains responsible for business-form processing after ColorShield authorization.
ColorShield does not need customer business-form field contents merely to validate form authenticity. It does not require password, card-number or IBAN values for form-authenticity validation, and it does not treat those field contents as ColorShield’s content store. Business payload handling stays with the customer application and its processors.
In BLOCK mode, protected submission can fail closed when fresh authorization cannot be safely confirmed for that interaction. The outcome applies to the protected form interaction, not a claim that the entire website is blocked. WARN and BLOCK are different policy modes and should be selected according to the customer’s risk posture.
No. ColorShield protects the authenticity of the form interaction before protected submit continues. Payment processors, gateways and fraud engines remain responsible for payment authorization, settlement and card-network processing. ColorShield is complementary infrastructure around form identity, not a replacement payment stack.
Managed Installation is optional ColorShield assistance with deployment and go-live checks. It may include Protected Flow configuration, SDK and server-bootstrap integration help, authorized-domain setup and launch verification. Access is temporary and revocable, such as a cPanel API token, limited SFTP or SSH credentials, or a developer-managed path. Never provide a cPanel password.
Use Request Protected Access for commercial and technical evaluation. After customer validation, ColorShield releases detailed SDK, bootstrap and deployment materials through approved onboarding. Public pages stay commercial-safe; full implementation guidance is provided for approved deployments rather than through the general contact form alone.
Request protected access for documentation, deployment discussion and Form Identity Protection on your sensitive forms.