Skip to content

Resources

Security Documents

WebCastle’s security policy library — what exists today, what is in development, and how to request documentation for a security review.

Reviewed 12 August 2026

Security documentation

WebCastle is building a formal security policy set. Several policies are drafted and moving through internal review; none has yet completed management approval, so none is published here as an approved document.

This is a deliberate choice. Publishing a policy implies it is approved, in force and being followed. Until that is true, this page reports the actual state of each document instead.

Where a security review needs detail before the policy set is published, the security team can provide written control descriptions covering the specific areas you need, under NDA where appropriate.

Available now

1 document

Documents WebCastle publishes today.

Privacy Policy

WebCastle’s published privacy policy, covering personal data handling, cookies, data subject requests and contact details.

AvailablePublic

Available now.

Owner: WebCastle

Open

In development

6 documents

Drafted and moving through internal review. Not yet approved for publication.

Information Security Policy

The overarching policy setting out WebCastle’s security objectives, governance, ownership and the scope of the security program.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Technical leadership

Access Control Policy

Account lifecycle, least privilege, privileged access, authentication requirements and periodic access reviews.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Technical leadership

Password & Authentication Policy

Password requirements, multi-factor authentication expectations and the handling of shared and default accounts.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Technical leadership

Incident Response Policy

How security incidents are identified, classified, contained, investigated, remediated and communicated.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Technical leadership

Data Protection Policy

Data classification, handling, storage, transmission, retention, deletion and customer data segregation.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Technical leadership

Secure Development Policy

Secure development lifecycle, code review, environment separation, dependency management and deployment controls.

In developmentOn request

Drafted and in internal review. Not yet approved for publication.

Owner: Engineering

Planned

4 documents

Scheduled for drafting as the security program develops.

Business Continuity Policy

Continuity approach, backup strategy, recovery planning, service restoration and customer communication.

PlannedOn request

Scheduled for drafting as part of the security program.

Owner: Technical leadership

Vulnerability Management Policy

Identification, assessment, prioritisation and remediation of vulnerabilities across applications and infrastructure.

PlannedOn request

Scheduled for drafting as part of the security program.

Owner: Engineering

Vendor Management Policy

Vendor selection, security review, ongoing oversight, data processing arrangements and offboarding.

PlannedOn request

Scheduled for drafting as part of the security program.

Owner: Technical leadership

Acceptable Use Policy

Expected use of WebCastle systems, accounts and devices, and the responsibilities that apply to everyone at WebCastle.

PlannedInternal

Scheduled for drafting as part of the security program.

Owner: Operations

Requesting documentation for a security review

If your review requires documentation that is not published here, contact the security team with the specific areas you need covered. WebCastle can complete your security questionnaire, provide written control descriptions, and sign an NDA where the discussion calls for it.