Organizations using AWS, Azure, Google Cloud, or a combination of providers
Protect
Encompass Managed Cloud Security
Keep AWS, Azure, and Google Cloud security current through recurring posture reviews, configuration drift checks, approved hardening, and clear monthly reporting.
Monthly security management with initial onboarding, monthly reporting, and quarterly planning. Coverage and engineering capacity are tailored to your environment.
Before we begin
Your engagement at a glance.
- Who it is for
- Organizations using AWS, Azure, Google Cloud, or a combination of providers
- What you receive
- Initial security baseline across agreed AWS accounts, Azure subscriptions, and Google Cloud organizations and projects; Monthly posture and configuration drift reviews against the agreed baseline; IAM, privileged access, service account, and workload identity review. Final deliverables are confirmed in your scope.
- Your participation
- Share your goals and connect us with the right technical contact. We handle the planning with you.
- How we verify completion
- Review completed work and supporting evidence against the agreed scope. The scope defines validation activities, any retesting, and responsibility for remediation. Record outstanding items and the handoff.
- Support after the project
- We can discuss recurring engineering, vulnerability management, or security leadership support. Ongoing work, coverage, reporting, and responsibilities are agreed separately.
What is included
What the recurring service includes
Final scope is tailored to your environment, objectives, and constraints. Typically includes:
This work often connects with Encompass Cloud Security Deployments, AWS, Azure & Google Cloud Security, and Managed SOC, EDR & MDR. Connecting these capabilities helps align adjacent controls, ownership, and remediation priorities.
- Initial security baseline across agreed AWS accounts, Azure subscriptions, and Google Cloud organizations and projects
- Monthly posture and configuration drift reviews against the agreed baseline
- IAM, privileged access, service account, and workload identity review
- Network exposure, storage permissions, encryption, and secrets review
- Maintenance of agreed cloud security policies and approved hardening changes
- Provider-native posture findings review and prioritization
- Logging, detection configuration, and escalation workflow checks
- Remediation backlog, exception tracking, and verification of agreed changes
- Monthly report covering completed work, outstanding risks, and next actions
- Quarterly security review and refreshed improvement roadmap
A strong fit for
Who managed cloud security is for
Cloud and infrastructure teams that need ongoing security ownership
Businesses whose security settings drift as workloads and access change
Engagement model
Establish the baseline. Maintain the controls. Verify progress.
Security engineers deliver the technical work. Security leadership aligns priorities, risk decisions, and stakeholders. Your agreed scope defines implementation, validation, and handoff responsibilities.
Establish
Inventory the agreed environment, review access and tooling, set the baseline, and prioritize onboarding fixes.
Maintain
Review changes and posture findings, tune controls, and implement approved improvements within the agreed monthly capacity.
Improve
Verify completed changes, report progress each month, and refresh priorities with stakeholders each quarter.
Service details
AWS, Azure, and Google Cloud on equal footing
Use the controls appropriate to each provider: AWS Security Hub CSPM and GuardDuty, Microsoft Defender for Cloud and Azure Policy, or Google Cloud Security Command Center and Organization Policy. We connect the findings to a shared remediation plan while retaining each platform's own access and configuration model.
Maintenance that leads to action
The recurring service includes agreed policy maintenance, configuration changes, and remediation within a defined engineering allowance. Larger deployments, migrations, penetration tests, and major remediation projects receive a separate scope before work begins.
A clear operating agreement
Your proposal identifies covered organizations, accounts, subscriptions, projects, workloads, service hours, review frequency, escalation targets, and engineering capacity. Tool subscriptions and provider consumption charges are identified separately. Around-the-clock SOC monitoring and incident response can be scoped separately.
Questions
Managed cloud security questions
The scoping call covers environment specific questions, dependencies, timing, and deliverables.
Can you support a single cloud or several providers?
Yes. The package can cover AWS, Azure, Google Cloud, or a connected environment across providers. We confirm the assets, access, tools, and responsibilities before onboarding.
How often do you review the environment?
The standard operating rhythm is a monthly posture and configuration review, monthly reporting, and a quarterly planning session. Additional checks and response targets are agreed in your proposal. Continuous tooling, where enabled, does not imply continuous human monitoring.
Do you implement the fixes?
Yes. Approved control maintenance and remediation are included within the engineering capacity in your agreement. Changes follow your approval and maintenance process. Work beyond that capacity is separately agreed.
Does this include 24/7 monitoring or penetration testing?
Those services are scoped separately. This package focuses on recurring cloud posture management, control maintenance, and remediation. Monitoring hours, response coverage, and any penetration testing are stated explicitly in the agreement.
Encompass Managed Cloud Security
Security expertise from leadership through delivery.
Tell us the problem, deadline, and where your team needs help. We will scope the security engineering, hands-on assessment or implementation, and leadership support that fits your engagement, with clear ownership and deliverables.