Defence in depth
Seven layers between an attacker and your content.
Forrit is secure by design. Seven layers protect your digital estate, from the edge of the network to the data at its core, so that if one control is ever bypassed, the next is already in place. Deploy Forrit in your own cloud tenant and you can add as many further layers around it as your security team wants.
Your own controls · optionalWhen Forrit runs in your cloud tenant, surround it with your existing firewalls, intrusion detection, network rules and monitoring.
Layer 1 Edge & attack surface protection
Reduce the attack surface and stop threats at the edge.
Layer 2 Architectural isolationThe Forrit difference
A compromised website should not mean a compromised CMS.
Layer 3 Identity & access security
Trust identity, not location. Only the right people and services get access.
Layer 4 Content & governance security
Control who can change what, who can publish it, and trace what happened.
Layer 5 Application & supply chain security
Reduce the chance a vulnerability ever reaches production.
Layer 6 Data & platform protection
Protect the data itself, not just the application accessing it.
Layer 7 Detection, assurance & response
Assume controls can fail, and be ready to detect and respond.
Your content and data
Certified and accountable
Standards you can put in front of your auditors.
Security claims are easy to make. Independent certification is not. Forrit Technology Ltd is certified to the standards procurement and risk teams ask for, and both the company and the platform are secure by design.
Certified
ISO/IEC 27001
Forrit Technology Ltd is certified to ISO 27001, the internationally recognised standard for information security management systems (certificate IT1361).
Certified
Cyber Essentials
The UK Government-backed scheme that the NCSC recommends as the minimum standard of cyber security for all organisations.
Member
Chartered Institute of Information Security
CIISec is the Royal Chartered body for cyber and information security professionals. Membership supports our commitment to equipping our team for the threats of tomorrow.
Member
Cyber and Fraud Centre – Scotland
Connecting us with law enforcement, government and industry experts to stay ahead of emerging cyber threats and fraud.
Layer 1 · Edge & attack surface protection
Reduce the attack surface and stop threats at the edge.
The outermost layer wraps your whole public digital estate. Malicious traffic is stopped before it reaches the application, and the underlying resources behind your sites are kept out of public view wherever they don't need to be exposed.
Edge and attack surface capabilities
Global front door
Traffic enters through a cloud front door service on a global edge network, built for performance, scale and security, before it reaches the application.
Web application firewall
A cloud-native WAF with custom and managed rule sets actively defends against the OWASP Top 10 web application security risks.
Bot and DDoS mitigation
Malicious bots and denial-of-service traffic are filtered using custom and managed rule sets, before they reach your site.
Encrypted connections
Sites are served over HTTPS, so traffic between your users and your digital estate is encrypted.
Minimal public exposure
Underlying resources aren't exposed publicly unless they need to be, and where they are, access is restricted as far as possible.
Real-time monitoring
Alerts and detailed reports show your team what is being blocked, so you can stay ahead of bad actors.
Layer 2 · Architectural isolation
A compromised website should not mean a compromised CMS.
This is what makes Forrit different. Rather than relying on the website's defences alone, Forrit is designed on the assumption that a public website could eventually be compromised, and contains the blast radius if it is.
Our one-way Airlock Publishing architecture separates the CMS from what the public sees. Content moves out from the CMS to dedicated Web and JSON delivery channels, and the public delivery tier provides no route back into the CMS.
How the one-way airlock works
A change is approved in the CMS, inside your secured environment
Approved content is pushed one way to front-end publishing services
Your public site serves published content only
Publishing services cannot access core CMS data, so there is no route back
Why architectural isolation matters
Separate editorial and delivery tiers
Editorial workloads run separately from dedicated Web and JSON delivery channels, so the systems your editors use are never the systems the public reaches.
Contained blast radius
We design on the assumption that a public website could one day be compromised. If it is, the impact is contained at the delivery tier, with no route back into your CMS.
Back-end data stays out of reach
Drafts, user accounts and core CMS data stay in the CMS. The services that face the public only ever hold what you have chosen to publish.
Proven under test
Airlock Publishing is a key reason independent risk and penetration testing finds the Forrit CMS so resilient to modern threats.
Layer 3 · Identity & access security
Trust identity, not location.
Only the right people and services should get access, and only to what they need. This layer covers both human and machine identity: strong sign-in for your teams, and credential-free authentication between platform services wherever possible.
Identity and access capabilities
Single sign-on and MFA
People sign in through your enterprise identity provider, with single sign-on, multi-factor authentication and conditional access.
Least-privilege access
Role-based access control gives every person and service only the permissions they need, and nothing more.
Restricted production access
Access to production environments is tightly restricted, with IP restrictions applied where appropriate.
Managed identities, not stored secrets
Platform services authenticate using managed identities wherever possible, removing stored credentials that could be leaked or reused.
- Optional service
Break-glass access
Controlled emergency access procedures, so urgent changes can still be made safely when normal routes are unavailable.
Layer 4 · Content & governance security
Control who can change what, and trace what happened.
CMS security isn't purely cyber security. The wrong change published at the wrong time can do as much damage as an attack, so Forrit protects against accidental or unauthorised change as well as external threats.
Every change has an owner, an approval and a record.
Content and governance capabilities
CMS roles and permissions
Decide exactly who can create, edit, approve and publish, enforced consistently across sites, teams, agencies and subsidiaries.
Approval workflows
Customisable workflows and tailored approval policies control what gets published, all tied back to each user's identity.
Release history and rollback
Changes are prepared in task branches and previewed before going live. Release history and full rollback let you reverse a change quickly.
Complete audit trail
Every CMS task, action and change is securely logged, giving you an audit history of who did what, and when.
AI under the same controls
Changes made by an authorised AI assistant through the Forrit MCP server land in task branches, just like changes made by people, so they are reviewed and approved before anything is published.
Layer 5 · Application & supply chain security
Build security into the software, not just around it.
Infrastructure controls only go so far. Forrit's engineering practice is designed to continuously reduce the chance that a vulnerability reaches production in the first place, from the first design decision to independent testing of every release.
Security at every stage of a release
Risk assessment and threat modelling at design
Secure coding standards and code review
Static analysis and dependency scanning
Vulnerability scanning and OWASP-aligned API security testing
Independent penetration testing before release
Application and supply chain capabilities
Secure development lifecycle
Risk assessment, threat modelling, secure coding standards and code review are built into how every Forrit release is designed and delivered.
Code and dependency analysis
Static application security testing and software composition analysis check our code and third-party dependencies for known vulnerabilities.
Penetration-tested releases
Every Forrit Platform product release is penetration tested. Optional penetration testing is available for your own environments too.
Managed patching and upgrades
Vulnerability scanning feeds managed patching and upgrades, so your platform doesn't fall behind on fixes.
Controlled build and release
Source code, builds and releases are managed through access-controlled DevOps tooling.
Reduced plugin risk
Your developers extend Forrit with components built using our .NET SDKs, supported by managed technology partners, rather than relying on unmanaged third-party plugins.
Layer 6 · Data & platform protection
Protect the data itself, not just the application around it.
This layer protects the content, assets and platform resources underneath everything else. Every file added to the Media Library is scanned for malware in near real time, and harmful content is stopped before it enters the CMS.
And because your environment can run in your own cloud subscription, the resources and the data stay under your ownership.
What happens when a file is uploaded
An editor uploads an image or document to the Media Library
The file is scanned for malware in near real time
Clean files join the Media Library; threats are blocked
Data and platform capabilities
Your cloud, your ownership
Your Forrit environment can live in your own cloud tenant and subscription. You own the resources, your assets stay in your subscription and you keep control of perimeter security, including any extra layers you add around Forrit.
Encryption
Encryption protects your content and data, and the connections that carry it.
Isolated resources and environments
Cloud resources are isolated and secured, and production is kept separate from development and test environments.
Restricted data access
Access to content, assets and underlying data is limited to the people and services that need it.
Backup and recovery
Backup and recovery controls protect your content and support fast service recovery if the worst happens.
External links audited
External URLs are audited from the very start of the publishing workflow, alongside media scanning.
Layer 7 · Detection, assurance & response
Assume controls can fail. Be ready to detect and respond.
No preventative control is perfect. The final layer closes the loop: monitoring and audit trails to spot problems, a defined route from detection to remediation, and independent assurance that the other six layers keep working.
From detection to remediation
Detect: security monitoring and alerts flag unusual activity
Escalate: incidents reach the right people, including your SOC
Investigate: logs and audit trails show what happened
Remediate: fix, recover and strengthen controls
Detection, assurance and response capabilities
Alerts and monitoring
Global real-time monitoring and system alerts tell you when a service isn't working as expected, so remediation can start straight away.
Logging and audit trails
Platform and CMS activity is logged, giving your team and investigators the evidence they need.
Vulnerability management
Vulnerabilities found by scanning and penetration testing are tracked and remediated.
SOC integration
Connect Forrit to your own Security Operations Centre or an approved third-party SOC, or add a managed SOC as an optional service.
- Optional service
Resiliency testing
Prove recovery before you need it, with resiliency testing of your environments.
ISO 27001 and Cyber Essentials governance
Our controls sit within an ISO 27001-certified information security management system, alongside Cyber Essentials certification.
Bank-grade operations
Fits your operating model, not the other way round.
Environments are deployed in minutes through the Forrit Service Delivery Hub, configured to support the most exacting security standards. Choose where your platform runs, add your own security controls around it, and bring in the services your risk team expects, as and when you need them.
Operating model options
- In your tenant
Add your own layers
Seven layers come as standard. Run Forrit in your own cloud tenant and you can surround it with the controls your security team already uses, such as firewalls, intrusion detection and network monitoring.
Public or sovereign cloud
Cloud native and deployable on leading public cloud platforms or with sovereign cloud providers, to meet data residency and sovereignty requirements.
Audited deployment in minutes
The Service Delivery Hub's seven-step process creates each environment accurately, with every deployment fully managed and audited.
Resilient under load
The platform scales dynamically to meet surges in demand, so performance stays consistent when traffic spikes.
Designed for fast recovery
High availability and, in the very worst case, fast service recovery are designed in from the start.
Regulation
Built to support the rules you are accountable to.
Forrit is designed to help regulated businesses meet modern operational resilience and security obligations. Here is how the platform maps to the regulations our customers ask about most.
| Regulation | What it asks of you | How Forrit helps |
|---|---|---|
| DORAEU Digital Operational Resilience Act | Financial entities must manage ICT risk, report major ICT-related incidents, test their digital operational resilience and manage ICT third-party risk. | Defence-in-depth architecture, penetration-tested releases, optional resiliency testing for your environments, real-time monitoring and alerts, and a full audit trail of every change. |
| NIS2EU Network and Information Security Directive | Essential and important entities must take appropriate cyber security risk-management measures and report significant incidents, with management bodies held accountable. | Edge protection, a secure development lifecycle with vulnerability management, enterprise identity with least-privilege access, SOC integration, and logs that support incident detection and investigation. |
| PRA operational resilienceUK Prudential Regulation Authority | Firms must identify important business services, set impact tolerances and be able to remain within them during severe but plausible disruption. | High availability and fast service recovery by design, dynamic scaling, Service Delivery Hub monitoring and optional resiliency testing to evidence recovery. |
| UK GDPR and EU GDPRGeneral Data Protection Regulation | Personal data must be protected with appropriate technical and organisational security measures. | Access controlled through enterprise identity and role-based permissions, CMS data kept away from the public site by Airlock Publishing, and sovereign cloud options for data residency. |
Compliance is a shared responsibility. Forrit provides capabilities that support your obligations; it does not replace your own risk, legal and compliance assessment.
Security questions, answered
Yes. Forrit Technology Ltd is certified to ISO 27001 for information security management and holds Cyber Essentials certification. Both the company and the platform are secure by design.
Airlock Publishing is Forrit's decoupled publishing architecture. Content is pushed out to front-end publishing services that cannot access core CMS data, so your back-end data can't be compromised through your public website. It is one layer of our defence-in-depth approach.
Forrit follows a Secure Development Lifecycle with threat modelling, secure coding standards and code review. Static application security testing, dependency analysis, vulnerability scanning and OWASP-aligned API testing run before release, and every Forrit Platform product release is independently penetration tested.
Forrit is built to help regulated businesses meet modern operational resilience standards. Our approach to threat intelligence, platform resilience, high availability and fast service recovery is designed to support compliance with the Prudential Regulation Authority, DORA and NIS2, backed by a full audit trail of every change.
Every file uploaded to the Media Library is scanned for malware in near real time. Your sites are protected by a web application firewall that defends against the OWASP Top 10 risks, malicious bots and DDoS attacks, with real-time alerts and reporting.
Yes. Every Forrit Platform product release is penetration tested, and optional penetration and resiliency testing is available for customer environments too.
Access is managed through enterprise identity management and role-based access control (RBAC), so users only have the privileges they need. Every CMS task, action and change is securely logged for future audit and review.
Yes. Forrit can integrate with your own Security Operations Centre or an approved third-party SOC, and a managed SOC is available as an optional service.
Yes. A Forrit environment can live within your own cloud tenant and subscription, so you own the resources, your assets stay in your subscription and you keep control over perimeter security.
Yes. As well as public cloud, Forrit can be deployed with sovereign cloud providers, helping organisations meet data residency, sovereignty and regulatory requirements. Talk to us about the provider and region that best suit your needs.
Changes made through the Forrit MCP server are made in task branches, just like changes made by people, so they can be reviewed and approved through your normal workflow before anything is published.