Start with the work your team needs done
Know which services fit, who owns each decision and what a useful operating agreement should deliver.
Start with the gaps in your current arrangements. Retain useful tools, define the responsibilities around them and commission the work that changes the outcome.
A good service agreement identifies the platforms covered, the people making decisions and the evidence that shows work has been completed. It should make the boundary with your internal team and other providers easy to understand.
Choose the relevant workstreams
- Microsoft 365 & Entra ID security — Establish a practical security baseline for the tenant, privileged identities, collaboration and managed devices.
- Google Workspace security — Define the controls and administrative routines protecting Workspace accounts, sharing and connected applications.
- AWS security assessment & hardening — Connect account structure, workload identities, exposure and security evidence to a manageable improvement plan.
- Azure & Google Cloud security — Specify platform configuration, workload identity and logging work across your selected Azure or Google Cloud environments.
- Identity & endpoint security programme — Bring privileged access, endpoint ownership and administrative practice into one accountable improvement programme.
- Security monitoring & SOC operating model — Define log coverage, triage ownership, escalation and response authority before buying or extending a monitoring service.
- Incident response readiness & retainer — Prepare the authority, access, contacts and commercial arrangements required to mobilise incident-response support.
- Virtual CISO & security leadership — Establish security ownership, a prioritised programme and a reporting rhythm that fits your management team.
- Assessment & compliance readiness — Determine the relevant baseline and evidence gaps before commissioning changes or making assurance claims.
- Penetration testing & vulnerability assessment — Use a defined technical assessment to validate important boundaries and verify selected remediation outcomes.
Fit the model to existing arrangements
Some organisations need an initial configuration review and a bounded implementation project. Others need recurring security leadership or help specifying monitoring and response operations. Describe those requirements separately. Existing products and providers can remain useful; address ownership gaps without assuming replacement.
Put the operating terms in writing
- Platforms, user populations, regions and exclusions.
- Responsibilities for administration, triage, changes and containment.
- Support hours, escalation routes and response targets.
- Data handling, access review, reporting and exit.
- Licences, implementation work and recurring fees.
Monitoring/SOC staffing and retainer terms require confirmation. This website does not promise a particular response time or activate emergency cover.
Prepare an informed request
Build your services RFP to match your platforms and support needs, or send an enquiry with your NDA or RFP.
Prepare a brief before the scoping call
Describe the technology you use, your existing security support and the outcomes you want. Review relevant service options, clarify operating responsibilities, then send the RFP with your NDA.
Use the free managed cybersecurity services brief builder to record objectives, assessment areas, constraints and NDA preferences. Review the proposed scope, then send it directly to Atlant Security through the contact form.
