Version 0.6.8 is available in PowerShell Gallery with bunch of bugfixes and new features.
First step of finally adding support for DataConnectors 😛
This new YAML example shows how you can configure multiple rules in one YAML file, with the same properties as in JSON format
Version 0.6.6 is available in PowerShell Gallery with bunch of bugfixes and new features.
From this version you can manage all type of Analytics rules from one template. The import and New-AzsentinelAlertRule functions are also optimized to import new rules much faster.
The layout of JSON file is updated to add support for the following Analytics rules:
JSON schema:
As you can see you can define all the rule types in the same template file. For each rule type you can find the properties on the following link. Below an example of a setting file containing all types of Analytic rules
You can also use the New-AzSentinelAlertrule function to create this kind of rules. You have now the switch “-Kind” that you can use to create other type of analytic rules.The default value is Scheduled rule. Below some examples:
New function to add comment to Azure Sentinel incidnent
Thanks to ramirezversion, This function return all the the Analytics rule templates
| Issue/PR ID | Fix by |
| #91 Update-AzSentinelIncident deletes various incident properties #89 | https://github.com/jholtmann |
| #87 Fixed an issue that caused enabled in alert groupingConfiguration to be set to true everytime due to an error in the code | https://github.com/ThijsLecomte |
| #78 Handle nextLink for Playbooks | https://github.com/stehod |
Good news guys! A new version of AzSentinel is available in PowerShell Gallery with bunch of bugfixes and new features.
Before we jump to all the good stuff, please let me thank everyone for their great feedback, support and mostly patience :p I know this version took really long and I received lots of messages. So sorry for that. The reason that it took longer is because I started my own company a couple of months ago and that kept me quite busy. As I promised I will keep maintaining this module until the Microsoft official PowerShell module is released. With that said, below you’ll find a list of changes in this new version.
In this version I have decided to drop the compare functionality. This means that from now on if an alert exists, you don’t get the popup message to confirm the new changes. Why, you ask. Well with the new Incident settings and Alert grouping, the Alert Class contained child objects and I had a really hard time to fix this in the compare functionality. So I asked around and understood that people don’t use this option that much, because most of the time deployments are done through Pipeline. So I still use it in some of the functions. Like to decide if a playbooks is assigned and if we need to remove it for example. Maybe we can bring this back in the next version. Let me know what you think about this decision and if you have any tips.
Another one is the output of “Import-AzSentinelAlertRule”. In the current version it’s returned with Write-Output and this has different result than the return function. Also, instead of writing each rule output one by one, I collect it in a temp variable and return at once. This also speeds up the loop process. So how do you know if your rule was created successful or not? Well I have added a new property value named “status” and it returns 3 values:
Created: if a rule doesn’t exist and is created;
Ok: if a rule exists and gets updated;
Failed: if there was an issue, with this one you will also get an error output at the beginning of the output (so scroll up).
In the upcoming version I will try to implement more performance optimization. If you have feedback please create an issue on GitHub or get in touch with me.
Also new in this version is support for Incidnet settings. You can use CreateIncidnet property in the JSON/YAML template or use the -CreateIncidnet switch when using New-AzSentinelAlertRule command. If you don’t configure this then the Microsoft default settings will be applied and your existing rules (JSON) are backwards compatible.
Also, this new version contains support for Alert grouping. You can configure this by adding the following properties to your JSON/YAML template for each rule or by using the New-AzSentinelAlertRule with the same properties. If you don’t configure this then the Microsoft default settings will be applied and your existing rules are backwards compatible.
or by using the following switches:
This is a new feature that Ofer has talked about in his latest presentation and in my opinion one of the must have features in Azure Sentinel Alert creation process. This option gives you the possibility to treat each event as a separate alert in Sentinel. This way instead of having one alert rule attached to your incident which contains 12 events, you can e.g. have 12 separate alerts assigned to one incident or 12 incidents each having one or more alerts. You can now enable this feature using -AggregationKind “AlertPerRow” in the New-AzSentinelAlertRule function or by using “aggregationKind”: “string” property in your template.
PLEASE DO NOT USE IN PRODUCTION, THIS FEATURE IS STILL IN PREVIEW!!
You have the following options:
– SingleAlert (default value)
– AlertPerRow
Also, you can use the Rename-AzSentinelAlertRule to rename your existing Rules.
In this version the Set-AzSentinel command will automatically enable the required Resource Providers if those are not enabled in your Subscription.
And finally, there were some issues with the number of playbooks returned. Shout-out to @stehod for solving this issue.
New version of AzSentinel is available in PowerShell Gallery with bunch of bugfixes and some new features. See below a list of the changes in this version.
From this version it’s possible to configure “Actions” for the Alert Rules through New-AzSentinelAlertRule by using the -playbookName switch. Or by configuring JSON “PlaybookName” property for each Alert rule. You only need to provide the logic APP name that you want to assign to your Alert rule. The function will automatically search the Logic App in your Subscription, the logic App is also tested to see if it’s compatible for Azure Sentinel!
This option is backwards compatible, if you don’t have the “PlaybookName” covered in your JSON template no changes will be applied. Thanks sbroosnokia for the feedback!
Below the new JSON layout:
To make this feature available the following new functions are added to AzSentinel:
| name | description |
| Get-AzSentinelAlertRuleAction | Use this function to see if a Alert rule has Action configured |
| New-AzSentinelAlertRuleAction | Configure Action for an existing Alert rule |
| Remove-AzSentinelAlertRuleAction | Remove configured Action |
In this version there is also an Update-AzSentinelIncident function available that you can use to update existing incidents. Not all the properties are currently available in Update function, but in feature version I will extend the possibilities. See below a list of current possibilities:
Close Incident with argument:
Change incident status to inProgress:
Add label to existing labels:
Below list of hotfixes:
| title | url | thanks to: |
| Time Format conflict #38 | https://github.com/wortell/AZSentinel/issues/38 | https://github.com/lunchbox-rcl |
| Issue using Import-AzSentinelAlertRule #27 | https://github.com/wortell/AZSentinel/issues/27 | https://github.com/garybushey |
“Azure Sentinel is a cloud-native SIEM that provides intelligent security analytics for your entire enterprise at cloud scale. Get limitless cloud speed and scale to help focus on what really matters. Easily collect data from all your cloud or on-premises assets, Office 365, Azure resources, and other clouds. Effectively detect threats with built-in machine learning from Microsoft’s security analytics experts. Automate threat response, using built-in orchestration and automation playbooks.” read more
Rules in Azure Sentinel create the basic logic on which Incidents get created. Currently the only way to add, change or delete rules is through the Azure portal. As we’re running a cloud Security Operations Center at Wortell with many customers connected, doing this manually is no option for us.
At the moment there is no documented API, ARM or PowerShell module to configure Azure Sentinel. After doing some research we were able to find the API’s that are currently being used by the Azure Portal and based on that we’ve written a PowerShell module to manage Azure Sentinel through PowerShell. Continue reading Azure Sentinel PowerShell Module
