You can set up Wallarm to log the following events in Microsoft Azure Sentinel:
Hits detected except for:
Vulnerabilities detected, all by default or only for the selected risk level(s):
- High risk
- Medium risk
- Low risk
Scope (exposed assets) changed: updates in hosts, services, and domains
On an hourly basis, you can get a notification with the number of requests processed during the previous hour
Setting up integration¶
In the Microsoft UI:
Proceed to the Sentinel Workspace settings → Agents → Log Analytics agent instructions and copy the following data:
- Workspace ID
- Primary key
In the Wallarm Console UI:
Open the Integrations section.
Click the Microsoft Sentinel block or click the Add integration button and choose Microsoft Sentinel.
Enter an integration name.
Paste the copied Workspace ID and Primary key.
Choose event types to be logged in Microsoft Sentinel. If the events are not chosen, then logs will not be sent.
Test the integration and make sure the settings are correct.
Delay in sending data to new workspaces
Creating a Workspace on Sentinel for Wallarm integration can take up to 1 hour for all services to function. This delay can result in errors during integration testing and usage. If all integration settings are correct but errors continue to appear, please try again after 1 hour.
Click Add integration.
Integration testing allows checking configuration correctness, availability of the Wallarm Cloud, and the notification format. To test the integration, you can use the button Test integration when creating or editing the integration.
The integration is tested as follows:
Test notifications with the prefix
[Test message]are sent to the selected system.
Test notifications cover the following events (each in a single record):
- New user in the company account
- Newly detected hit
- Newly discovered IP in the company scope
- New trigger in the company account
- Newly discovered security vulnerability
Test notifications include test data.
You can find Wallarm logs in your Microsoft Workspace → Logs → Custom Logs, e.g. the test
create_user_CL log in Microsoft Sentinel looks as follows:
Types of Wallarm logs¶
Overall, Wallarm can log in Sentinel the records of the following types:
|Event||Sentinel log type|
|New hit|| |
|New user in a company account|| |
|Deletion of a user from a company account|| |
|User role update|| |
|Deletion of an integration|| |
|Disabling an integration|| |
|New application|| |
|Deletion of an application|| |
|Application name update|| |
|New vulnerability of a high risk|| |
|New vulnerability of a medium risk|| |
|New vulnerability of a low risk|| |
|New rule|| |
|Deletion of a rule|| |
|Changes of an existing rule|| |
|New trigger|| |
|Deletion of a trigger|| |
|Changes of an existing trigger|| |
|Updates in hosts, services, and domains in exposed assets|| |
|Changes in API inventory (if the corresponding trigger is active)|| |
|Amount of attacks exceeds the threshold (if the corresponding trigger is active)|| |
|New denylisted IP (if the corresponding trigger is active)|| |
To update the settings of active integration:
Open an active integration.
Make required changes and click Save.
To stop sending reports and notifications temporarily, you can disable the integration:
Open an active integration and click Disable.
To re-enable sending reports and notifications, open the disabled integration and click Enable.
Disabling the integration is the system event. If you receive system notifications, messages about disabled integration will be sent to the configured system.
To stop sending reports and notifications permanently, you can delete the integration. Deleting an integration cannot be undone. The integration will be removed from the list permanently.
Open integration and click Delete.
Confirm the action.
Deleting the integration is the system event. If you receive system notifications, messages about deleted integration will be sent to the configured system.