Azure Sentinel EPS & Log Size Calculator - Usage Disclaimer

By
I provide this Azure Sentinel Sizing Calculator as a tool to help customers analyze resources needed for Azure Sentinel deployment, and the Calculator is provided solely for your convenience in that regard. Specifically, the number of required resources reflected in the calculator are estimates based solely on my experience. The actual resource will vary based on many factors associated with your organization’s specific needs, and the figures reflected in the calculator are not a guarantee of any actual resource needs or of any savings that may result from using any Azure solutions. I provide the Azure Sentinel Sizing Calculator and all information included here “as is” and with all faults to the extent permitted by law. I hereby disclaim all representations and warranties of any kind, whether express, implied, or statutory, with respect to the use of the calculator or any information included here. In no event, I shall be liable for any damages, whether direct, indirect, consequential, incidental, special, punitive, exemplary or otherwise, including without limitation operational losses, loss of earnings, loss of data, business interruption, interest loss or any other commercial damages or losses arising out of or in any way related to the use of or inability to use, or any reliance on, the calculator or any information included here, including, without limitation any liability for: You hereby release me from any and all liability arising from or related to the calculator or its use.

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

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...
Read more