Sentinel POC- Architecture and Recommendations For MSSPs (Part 2)

By Ashwin Venugopal -

 




To read part 1, please click here
To read part 3, please click here
To read part 4, please click here
To read part 5, please click here







B2B or GDAP 

In order to access tenant level services, tenant level access is required. However, while testing Sentinel, this becomes more important because there are links provided to Microsoft Defender 365 and to make those links to work properly, the user must have access to the services.

GDAP and B2B offers the ability to access tenant level services. Everyone is quite familiar with B2B, which is available for all tenants to invite guests into their tenant to collaborate. But, some partners may have either compliance or cybersecurity insurance requirements preventing them from having an identity in their customers' tenants. Granular Delegated Admin Privileges (GDAP) is exclusively available to Cloud Solution Providers (CSPs) and it is configured by Partner Center. This one can help in accessing customer resources securely and does not require an identity in the customer's tenant.

Partners can choose either GDAP or B2B to access the tenants acting as customer tenant during the POC. For the purpose of Sentinel POC, the access and the behavior of using GDAP vs B2B is equivalent. However, if it is required to follow the same procedures during POC expected to be followed during go-live, then, it is recommended to configure GDAP. But, for simply testing the Sentinel's features for a period of time, then B2B can be used. 

More on CSPs

Cloud Solution Providers (CSPs) partners can create subscriptions for customers which is great for the customers not having security subscription and migrating from legacy SIEM solutions. Although this may not be used in POC, but can be tested according to the requirements of POC. That subscription will then be billed through the partner, but will remain associated with the customer's tenant. 

Where is data?

The customer's security subscription, where Sentinel is onboarded, should always be associated with the customer's tenant. Sentinel artifacts like, analytics rules, workbooks, automation rules, playbooks, etc., can easily exist either on MSSP workspace or the customer workspace. It should also be noted that features such as UEBA, and connectors like Defender 365, will only work with supported configuration depending on the data being ingested into the customer's workspace. The other types of data like Threat Intelligence (TI) data, can also be ingested into MSSP tenant.










To read part 1, please click here
To read part 3, please click here
To read part 4, please click here
To read part 5, please click here






























Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more