Design Planning (Part 3)

By Ashwin Venugopal -

 





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 stored in Microsoft Sentinel but cannot modify any settings.
  • Microsoft Sentinel Responder- Can query the log data , can view and update incidents raised by security rules, but cannot modify alert rules. 
  • Microsoft Sentinel Playbook Operator- Can view and run automation playbooks. 
  • Microsoft Sentinel Automation Contributor- Not applicable to users, is used to grant the ability to associate playbooks with automation rules. 

Also, there are additional roles that are required to fully configure and use Microsoft Sentinel:

  1. Logic App Contributor- For creation and management of SOAR playbooks.
  2. Workbook Contributor- For creation and management of workbooks.
  3. Workbook Reader- For accessing/reading workbooks. 

Moreover, custom RBAC roles can be created and associated with the Microsoft Sentinel instance. The roles can applied at the subscription or resource group level with the recommendation being to provide the minimum permissions required to perform the job. However, if access to data is required for only a subset of data in Microsoft Sentinel tables, read-only dashboards can be provided or the data can be presented according to the custom queries or via Microsoft Power BI. 

Estimation of Log Ingestion Volume and Pricing Model

The estimation of future log ingestion is a challenging exercise. Selecting a sample of log and configuring them to send full logs for a typical day or week is often the most precise way to estimate the log ingestion volume. Based on the expected logging volume, a pricing model can be selected to take advantage of the commitment tier discounts offered by Microsoft. 

Architecture Design Output

At the end of the high-level design phase, the following items should be decided and documented:
  • Azure region used for Microsoft Sentinel Log Analytics workspace or workspaces.
  • Azure subscription, resource group, and log analytics workspace, including naming convention and tags.
  • Azure AD groups and the RBAC to be applied to each.
  • Log sources in scope (on-premises, cloud, SaaS).
  • Microsoft Sentinel data connectors to be developed (if applicable).
  • On-premises syslog collectors (quantity, location, operating system type, any extra configuration)
  • Initial list of use cases to be implemented.
  • Internet/VPN/LAN/WAN connectivity between log sources and Microsoft Sentinel.
  • Estimated log ingestion volume (GB/day). Data retention policy (in days or months).
  • Pricing model versus reserved capacity, depending on the estimated log ingestion volume. 

Conclusion

This ends the topics related to the Architecture Planning and Considerations with all the key factors.




To read part 1, please click here
To read part 2, 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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more