User Profile
Javier-Soriano
Microsoft
Joined 8 years ago
User Widgets
Recent Discussions
Re: Azure Sentinel MSP - Non-Scheduled Alert Queries
No problem. Also, if you at some point have to go over the 10 workspaces limit that we support in the cross-ws incident view, you can always use this workbook as the central management pane: https://github.com/Azure/Azure-Sentinel/blob/master/Workbooks/SentinelCentral.json1.2KViews0likes0CommentsRe: Azure Sentinel MSP - Non-Scheduled Alert Queries
Yes, but protecting intellectual property only makes sense for scheduled rules, For non-scheduled rules, there's really no IP to protect, right? The best practices is to ONLY use cross-ws analytics rules when there's a need to protect IP. Regards1.3KViews0likes2CommentsRe: Azure Sentinel Automation (Preview) - Issue with Permission assignment
Are you also working in a Lighthouse setup or in a single AAD tenant setup? if you're working in a single tenant, these instructions should work: https://docs.microsoft.com/en-us/azure/sentinel/tutorial-respond-threats-playbook#respond-to-incidents For the multi-tenant scenario, we have now added the proper instructions here: https://docs.microsoft.com/en-us/azure/sentinel/automate-incident-handling-with-automation-rules#permissions-in-a-multi-tenant-architecture12KViews0likes0CommentsRe: Azure Sentinel Automation (Preview) - Issue with Permission assignment
For scenario #1...how can you have owner on the subscription via Lighthouse? that role is not allowed in an Lighthouse delegation: https://docs.microsoft.com/en-us/azure/lighthouse/concepts/tenants-users-roles#role-support-for-azure-lighthouse For scenario #2, azure security insights app must have Azure Sentinel Automation Contributor (not Azure Sentinel Contributor).12KViews0likes2CommentsRe: Azure Sentinel Automation (Preview) - Issue with Permission assignment
Ok, that requires additional permissions. You need to grant Azure Sentinel Automation Contributor permissions to the Azure Security Insights app in the service provider tenant, to the RG where the playbooks are in the customer tenant. So basically you need to include this additional authorization in your Azure Lighthouse delegation. Regards12KViews0likes11CommentsRe: Creating Sentinel instances with code
Our stable API has the list of things that can be deployed programatically: https://docs.microsoft.com/en-us/rest/api/securityinsights/dataconnectors/createorupdate There's other connectors outside of that list that are based on diagnostics settings or solutions on top of the Log Analytics workspace, that can also be enabled programatically. Regards1.9KViews0likes0CommentsRe: Azure Sentinel Multi tenant/MSSP Playbooks
mperrottayou should be able to select a playbook in the MSSP tenant as an automatic response to an analytics rule created in the customer tenant. If you don't see those playbooks, it could be because you're lacking permissions to see the resource group where the playbooks are located or because you don't have a Logic App role granted in the MSSP tenant (or both!)7.3KViews0likes1Comment- 2.1KViews0likes0Comments