Azure Monitor No Diagnostic Settings

Risk Level: Low

Description  

The plugin checks that the Azure Monitor account is configured. This simply implies that there are diagnostic settings configured to instruct the monitor platform on what kind of data and instances needs to be archived.

About the Service

Monitor: As the name suggests Azure monitor service, allows users to view and analyze all the activities around the azure platform and on-premises environment. Through Azure Monitor, users take an insight of the applications, VMs or containers, visualize the workbooks and dashboards, analyze the Metric analytics and log analytics for issues, respond to alerts and integrate logic apps and export APIs.

Impact

In case the diagnostic setting(s) is not set, the monitor platform will not be able to take action of collecting logs of the required categories which are essential to be collected and stored for later analysis. 

Steps to Reproduce

1. Log in to the Azure portal.
2. Go to Monitor under Services or type “Monitor” in the search box.
   
3. From the navigation panel, go to Activity log.
   
4. Go to the Diagnostic tab. Verify that a diagnostic rule is present. If not, please visit the Steps to Remediate section.
   

Steps for Remediation

1. Login to the Azure portal.
2. Go to Monitor under Services or type “Monitor” in the search box.
   
3. From the navigation panel, go to Activity log.
   
4. Go to the Diagnostic tab. Click on Add diagnostic setting under Diagnostic settings.
   
5. Fill in the Diagnostic setting name field, under logs select all the categories (we recommend selecting all the categories) and select a destination field. Click on the Save button and wait for the changes to get saved. 
   

Please feel free to reach out to support@pingsafe.ai with any questions that you may have.

Thanks

PingSafe Support