Azure environments tend to grow faster than the controls around them. PASY Technology brings yours back to a known, defensible state in stages: lock down access and exposed services first, standardize configuration next, then automate detection and response so the environment stays that way.
Close the gaps attackers use first
We reduce the attack surface in order of risk: who can administer Azure, what is exposed to the internet, and how data is protected and recovered.
First 90 days
- Enable endpoint protection on every virtual machine
- Disable insecure protocols
- Apply least-privilege access with PIM and Azure role-based access control
- Enable just-in-time access to management ports and Azure resources
- Run access reviews for privileged Azure roles
- Apply resource locks, and enable soft delete and purge protection for storage and key vaults
Months 3 to 6
- Administer Azure from privileged access workstations
- Restrict resource access to trusted networks and devices
- Enforce encryption in transit
- Define and enforce desired state configuration for virtual machines
- Harden network security group rules
- Enable vulnerability assessment and auditing
Month 6 onward
- Standardize resource configuration with Azure Policy
- Apply security baselines to virtual machines
- Enforce backup and data retention for business continuity
- Review geo-replication settings for storage accounts
See what is happening in your environment
We make sure activity across your subscriptions is logged, collected in one place and actively examined.
First 90 days
- Audit network usage to confirm which resources truly need to be public
- Begin Microsoft Sentinel data collection
Months 3 to 6
- Enable monitoring and auditing across all resources
- Build Microsoft Sentinel threat hunting and investigation queries
Month 6 onward
- Automate and streamline incident response workflows
Act quickly and learn from every incident
We build the routines that turn findings into fixes, and make the results measurable.
First 90 days
- Apply missing software updates
- Test application compatibility before security recommendations are enforced
- Configure automated security notifications
Months 3 to 6
- Define and track security KPIs so progress is visible to leadership
Month 6 onward
- Enable automated investigation and remediation in Microsoft Sentinel
Work that runs alongside every phase
Start with an Azure security review
Tell us about your Azure environment and we will outline where a phased program would begin for your organization.
Talk to Our Team →