Skip to main content
Checks that Azure NSG flow logs are captured.

​
About

When you connect Microsoft Azure to DSALTA, the platform retrieves the list of resources in your environment using read-only API access. DSALTA then checks whether this configuration is in place. If it is not, DSALTA activates this check so you can remediate it.

​
Why This Matters

Without audit logs you cannot detect unauthorized activity, investigate an incident, or prove what happened during an audit. Comprehensive, retained logs are the forensic backbone of incident response and are mandated by SOC 2, ISO 27001, and HIPAA.

​
How to Fix

Before you begin
  • Ensure you have Contributor access to the Azure subscription.
Archive activity / flow logs
  1. Sign in to the Azure Portal.
  2. For activity logs, open Monitor → Activity log → Export Activity Logs, add a diagnostic setting, and archive to a storage account with 365-day retention.
  3. For NSG / VNet flow logs, open Network Watcher → NSG flow logs, turn the log On, select a storage account, and set 90-day retention.
Once logs are captured and retained, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Microsoft Azure integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Azure.