Ops guide - add file

Author: cwatson-cat

articles/sentinel/ops-guide/ops-guide.md

@@ -0,0 +1,50 @@
+---
+title: Operational guide - Microsoft Sentinel
+description: Learn about the operational recommendations to help security operations teams to plan and run security activities.
+ms.date: 06/18/2024
+ms.topic: reference
+ms.author: cwatson
+author: cwatson-cat
+appliesto:
+  - Microsoft Sentinel in the Azure portal and the Microsoft Defender portal
+---
+
+# Microsoft Sentinel operational guide
+
+This section of the Microsoft Sentinel documentation helps security operations (SOC) teams and security administrators to plan and run regular security activities with Microsoft Sentinel.
+
+## Daily tasks
+
+Schedule the following activities daily.
+
+|Task|description|
+|---|---|
+|**Triage and investigate incidents**|Review the Microsoft Sentinel **Incidents** page to check for new incidents generated by the currently configured analytics rules, and start investigating any new incidents. For more information, see [Investigate incidents with Microsoft Sentinel](investigate-cases.md).|
+|**Explore hunting queries and bookmarks**|Explore results for all built-in queries, and update existing hunting queries and bookmarks. Manually generate new incidents or update old incidents if applicable.  For more information, see:</br></br>- [Automatically create incidents from Microsoft security alerts](create-incidents-from-alerts.md)</br>- [Hunt for threats with Microsoft Sentinel](hunting.md)</br>- [Keep track of data during hunting with Microsoft Sentinel](bookmarks.md)|
+|**Analytic rules**|Review and enable new analytics rules as applicable, including both newly released or newly available rules from recently connected data connectors.|
+|**Data connectors**| Review the status, date, and time of the last log received from each data connector to ensure that data is flowing. Check for new connectors, and review ingestion to ensure set limits aren't exceeded. For more information, see [Data collection best practices](best-practices-data.md) and [Connect data sources](connect-data-sources.md).|
+|**Log Analytics Agent**| Verify that servers and workstations are actively connected to the workspace, and troubleshoot and remediate any failed connections.   For more information, see     [Log Analytics Agent overview](../azure-monitor/agents/log-analytics-agent.md).|
+|**Playbook failures**| Verify playbook run statuses and troubleshoot any failures.   For more information, see  [Tutorial: Respond to threats by using playbooks with automation rules in Microsoft Sentinel](tutorial-respond-threats-playbook.md).|
+
+## Weekly tasks
+
+Schedule the following activities weekly.
+
+|Task|description|
+|---|---|
+|**Content review of solutions or standalone content**| Get any content updates for your installed solutions or standalone content from the [Content hub](sentinel-solutions-deploy.md). Review new solutions or standalone content that might be of value for your environment, such as analytics rules, workbooks, hunting queries, or playbooks.|
+|**Microsoft Sentinel auditing**| Review Microsoft Sentinel activity to see who updated or deleted resources, such as analytics rules, bookmarks, and so on. For more information, see [Audit Microsoft Sentinel queries and activities](audit-sentinel-data.md).|
+
+## Monthly tasks
+
+Schedule the following activities monthly.
+
+|Task|description|
+|---|---|
+|**Review user access**| Review permissions for your users and check for inactive users. For more information, see [Permissions in Microsoft Sentinel](roles.md).|
+|**Log Analytics workspace review**| Review that the Log Analytics workspace data retention policy still aligns with your organization's policy.  For more information, see  [Data retention policy](/workplace-analytics/privacy/license-expiration) and [Integrate Azure Data Explorer for long-term log retention](store-logs-in-azure-data-explorer.md).|
+
+
+## Related content
+
+- [Deployment guide for Microsoft Sentinel](../deploy-overview.md)