Identity
Identity & access
IAM, single sign-on and access policy. Our records engagement runs SSO through Cognito and Microsoft Entra ID, so the archive answers to the same directory as everything else.
The Stack Behind Every Engagement
Four disciplines, one accountable team - depth where it actually changes the outcome.
Identity, network and endpoint security, with the audit trail to prove it.
Engineers who have run the tooling rather than only installed it - and a delivery model where the security posture is part of the cutover rather than a follow-up ticket.
Decided during the work, not after it
How it is delivered
When does security actually get decided?
Almost never on a security engagement. It is decided when the target architecture is designed, when the identity model is chosen, when someone decides where the data will physically sit - all of which happen inside a migration, a build or an onboarding, weeks before anyone runs a scan.
So the same people appear in both places. We staff security as its own discipline, and we put its decisions inside the delivery: identity and access policies designed with the target architecture, encryption and audit readiness in the migration plan, and postures hardened at the stabilization phase rather than raised as findings afterwards.
What we staff
SOC and SIEM - engineers who have operated the tooling, not only deployed it
IAM - identity and access as a design decision, not a permissions cleanup
Network security - VPN and firewalls across the estate you actually have
Endpoint security - protection on the devices the work is done from
What we build in
Identity and access policies - designed alongside the target architecture
Encryption and data protection - including where the data is allowed to sit
Audit readiness - compliance auditing as part of the plan, not a later exercise
Hardened postures - security and compliance tightened before handover
Six areas we cover
Disciplines
- Network
Network security
VPN and firewalls, configured against the estate as it is rather than as the diagram says - including the hybrid cases where half of it is still on-premise.
- Endpoint
Endpoint protection
Protection on the devices work is actually done from, managed as part of the IT service rather than as a separate product nobody owns.
- Detection
SOC & SIEM
Monitoring and correlation run by people who have carried the pager. Detection is only useful if somebody is on the other end of the alert.
- Data
Data protection
Encryption in transit and at rest, and deployment models chosen for the privacy rules that apply - including fully on-premise where nothing may leave the building.
- Compliance
Compliance & governance
Compliance auditing, governance and audit readiness, so the evidence exists before it is asked for rather than being assembled under deadline.
Where it shows up in every other engagement
Across the work
Cloud migration - identity and access policies, encryption and audit readiness designed into the target architecture, with postures hardened at stabilization
Infrastructure & IT - secure, compliant and scalable environments, with endpoint protection, compliance auditing and data encryption in the managed service
Applications - a security-first mindset through the build, and enhanced security as part of any modernization
Regulated deployments - secure on-premise deployment where privacy rules mean the data cannot leave your own infrastructure
Security work already running
In production
Threat Intelligence
Continuous NLP monitoring of public channels for hate speech, threats and risky behavior, with real-time alerting and escalation for early intervention.
Read the caseDocument OCR
An archive of legal documents made searchable under strict privacy demands, met through secure on-premise deployment rather than by policy alone.
Read the case
Common Questions About Cybersecurity
FAQ
Six areas: identity and access management, network security, endpoint protection, SOC and SIEM monitoring, data protection and encryption, and compliance and governance.
Yes, staffed by engineers who have operated the tooling rather than only deployed it - detection is only useful if someone is on the other end of the alert.
Identity and access policies, encryption and audit readiness are designed into the target architecture, and security postures are hardened at the stabilization phase rather than raised as findings afterwards.
Yes. Where privacy rules mean data cannot leave your infrastructure we deploy fully on-premise - as in our Document OCR engagement for a legal archive.
Yes. Compliance auditing and governance are part of the plan, so the evidence exists before an auditor asks for it.
Where is your exposure
Whether it is an estate to assess, an identity model to fix, or a migration that needs its posture designed rather than reviewed - tell us what you are protecting.