⚡ SAFETY STACK · FREE WITH EVERY PACKAGE • CONDUCTOR (auto-deploy) • REASON (3-candidate think-first) • PHOENIX (cascade recovery) • DR-GUARD (region failover) • NEVER BREAKS ANYTHING
LIVE FEED
AZURE

LIVE SECURITY ALERTS

REAL-TIME SOC DASHBOARD • AI-POWERED DETECTION • ALL CLOUDS
AZURE
Real-time security findings from Azure — flagged by 33 AI Agents. Every alert includes the resource, the violation, the compliance framework, and step-by-step remediation.
0
CRITICAL
0
HIGH
0
MEDIUM
0
RESOLVED
CLOUD:
SEVERITY:

ALERT FEED

19 alerts
CRITICAL AZURE Storage Account Missing Encryption for PHI Data OPEN 2 min ago ▼
RESOURCE
pyxhealthprodstore01
Type: Microsoft.Storage/storageAccounts
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.Storage/storageAccounts/pyxhealthprodstore01
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
HIPAA §164.312(a)(2)(iv) HITRUST 09.x NIST SC-28
TIMESTAMP
2026-04-16T14:23:07Z
WHY FLAGGED
Storage account contains PHI (Protected Health Information) in HL7/FHIR blobs but does NOT have customer-managed key (CMK) encryption enabled. Data-at-rest encryption uses only Microsoft-managed keys, violating HIPAA encryption requirements for ePHI storage.
HOW TO FIX
1. Create a Key Vault key (RSA 2048+) in the same region
2. Enable CMK encryption: Storage Account → Encryption → Customer-managed keys
3. Select the Key Vault key and enable automatic key rotation
4. Verify encryption status in Azure Policy
CRITICAL AZURE NSG Allows SSH (Port 22) from Internet 0.0.0.0/0 OPEN 4 min ago ▼
RESOURCE
nsg-pyx-prod-001
Type: Microsoft.Network/networkSecurityGroups
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.Network/networkSecurityGroups/nsg-pyx-prod-001
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
HIPAA §164.312(e) NIST SC-7 PCI-DSS 1.3 SOC 2 CC6.6
TIMESTAMP
2026-04-16T14:22:45Z
WHY FLAGGED
Network Security Group has an inbound rule allowing SSH (TCP/22) from source 0.0.0.0/0 (any internet address). This exposes the production environment to brute-force attacks, credential stuffing, and unauthorized remote access from anywhere on the internet.
HOW TO FIX
1. Remove the Allow-SSH-Inbound rule from nsg-pyx-prod-001
2. Restrict SSH to specific IP ranges (corporate VPN CIDR blocks only)
3. Deploy Azure Gatekeeper for secure jump-box access
4. Enable Just-In-Time VM Access in Microsoft Defender
HIGH AZURE SQL Server Public Network Access Enabled INVESTIGATING 7 min ago ▼
RESOURCE
sqlsrv-pyx-prod
Type: Microsoft.Sql/servers
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.Sql/servers/sqlsrv-pyx-prod
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
HIPAA §164.312(a)(1) SOC 2 CC6.1 NIST AC-4
TIMESTAMP
2026-04-16T14:20:31Z
WHY FLAGGED
SQL Server has public network access set to "Enabled" and a firewall rule allowing 0.0.0.0 - 255.255.255.255 (AllowAllWindowsAzureIps). The database stores PHI and is directly reachable from the public internet, bypassing network isolation controls.
HOW TO FIX
1. Disable public network access on sqlsrv-pyx-prod
2. Configure Private Endpoint for VNet-only access
3. Remove the AllowAllWindowsAzureIps firewall rule
4. Enable Advanced Threat Protection for SQL
HIGH AZURE Key Vault Soft Delete and Purge Protection Disabled OPEN 9 min ago ▼
RESOURCE
kv-pyx-prod-001
Type: Microsoft.KeyVault/vaults
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.KeyVault/vaults/kv-pyx-prod-001
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
HITRUST 09.l NIST SC-12 SOC 2 CC6.1
TIMESTAMP
2026-04-16T14:19:58Z
WHY FLAGGED
Key Vault does not have soft-delete or purge protection enabled. Accidental or malicious deletion of encryption keys, secrets, or certificates would be permanent and unrecoverable, potentially causing data loss for all resources depending on these keys.
HOW TO FIX
1. Enable soft-delete: az keyvault update --name kv-pyx-prod-001 --enable-soft-delete true
2. Enable purge protection: az keyvault update --name kv-pyx-prod-001 --enable-purge-protection true
3. Set retention to 90 days (default)
4. Verify in Azure Policy compliance
HIGH AZURE AKS Cluster Kubernetes RBAC Not Enabled OPEN 11 min ago ▼
RESOURCE
aks-pyx-prod
Type: Microsoft.ContainerService/managedClusters
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.ContainerService/managedClusters/aks-pyx-prod
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
SOC 2 CC6.1 NIST AC-6 HIPAA §164.312(a)(1)
TIMESTAMP
2026-04-16T14:18:42Z
WHY FLAGGED
AKS cluster does not have Kubernetes RBAC enabled. All authenticated users have full cluster-admin privileges. Containers running in the cluster can access any namespace, secret, or config map without restriction, violating least-privilege access controls.
HOW TO FIX
1. Enable Azure AD integration + Kubernetes RBAC on the cluster
2. Create namespace-scoped Roles and RoleBindings
3. Remove default cluster-admin binding for all users
4. Enable Azure Policy for AKS to enforce pod security standards
MEDIUM AZURE TLS 1.0 Enabled on App Service (Deprecated Protocol) INVESTIGATING 14 min ago ▼
RESOURCE
app-pyx-portal
Type: Microsoft.Web/sites
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-prod/providers/Microsoft.Web/sites/app-pyx-portal
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
PCI-DSS 4.1 NIST SC-8 HIPAA §164.312(e)(1)
TIMESTAMP
2026-04-16T14:17:14Z
WHY FLAGGED
App Service has minimum TLS version set to 1.0. TLS 1.0 has known vulnerabilities (BEAST, POODLE) and is deprecated by all major standards bodies. Patient portal traffic may be intercepted using protocol downgrade attacks.
HOW TO FIX
1. Set minimum TLS version to 1.2: App Service → TLS/SSL Settings → Minimum TLS Version → 1.2
2. Test client compatibility (all modern browsers support TLS 1.2+)
3. Update Azure Policy to enforce TLS 1.2 minimum across all App Services
MEDIUM AZURE Storage Account Allows Anonymous Public Blob Access OPEN 16 min ago ▼
RESOURCE
pyxhealthdevstore
Type: Microsoft.Storage/storageAccounts
ID: /subscriptions/7e5a...d3f1/resourceGroups/rg-pyx-dev/providers/Microsoft.Storage/storageAccounts/pyxhealthdevstore
LOCATION
Cloud: Azure
Region: East US 2
Subscription: PYX-Health-Production
COMPLIANCE FRAMEWORKS
HIPAA §164.312(a)(1) NIST AC-3
TIMESTAMP
2026-04-16T14:16:03Z
WHY FLAGGED
Storage account has "Allow Blob public access" set to Enabled. Any container set to public access level will expose blobs to the entire internet without authentication. Dev environments often contain copies of production data including PHI.
HOW TO FIX
1. Disable public blob access: Storage Account → Configuration → Allow Blob public access → Disabled
2. Audit all containers for public access level settings
3. Use SAS tokens or Azure AD for authorized access only
4. Deploy Azure Policy to prevent re-enabling
-->

ALERT SUMMARY

ALERTS BY CLOUD PROVIDER
CLOUD CRITICAL HIGH MEDIUM TOTAL
Azure 2 3 2 7
TOTAL 7 7 5 19
ALERTS BY COMPLIANCE FRAMEWORK
FRAMEWORK FINDINGS CRITICAL HIGH
HIPAA 14 6 4
NIST 800-53 13 5 5
PCI-DSS 6 4 1
SOC 2 7 1 4
HITRUST 4 1 2
CIS Benchmarks 8 4 3

STOP THREATS BEFORE THEY BECOME BREACHES

Real-time alert feed from Azure.
33 AI Agents. Azure cloud. One dashboard. — Deployed in minutes.

REQUEST FREE AUDIT VIEW PRICING