Author
Abstract
The growing sophistication and volume of cyberattacks have outpaced the capacity of manual security operations to detect and contain threats within an acceptable time window. Cloud-native Security Information and Event Management (SIEM) platforms combined with Security Orchestration, Automation, and Response (SOAR) capabilities have emerged as a response to this gap, enabling organizations to correlate telemetry across large, distributed environments and to trigger automated containment actions without waiting for manual analyst intervention. Microsoft Azure Sentinel (now marketed as Microsoft Sentinel) is one such platform, combining a cloud-scale data lake, machine-learning-based analytics, and low-code automation playbooks within a single service. This article examines how Azure Sentinel can be configured to detect a range of common cyberattack scenarios and to trigger automated response actions that contain threats before they escalate, spanning intrusion detection research, SIEM and SOAR architecture studies, threat intelligence frameworks including MITRE ATT&CK, and automated incident response systems, the article proposes an end-to-end detection-and-response pipeline architecture for Sentinel, compares its core components against their underlying detection and response functions, and maps common attack scenarios to specific Sentinel-based detection logic and automated mitigations. The findings indicate that Sentinel's integration of data aggregation, behavioral analytics, and orchestrated response substantially reduces mean time to detection and containment relative to manually operated security operations, provided that organizations invest in tuning analytics rules, mapping detection logic to a recognized threat taxonomy, and maintaining human oversight of automated response actions. The article concludes with practical recommendations for security operations teams adopting Azure Sentinel.
Suggested Citation
Handle:
RePEc:cxi:ijans0:v:2:y:2024:i:2:id:1074
DOI: 10.61424/ijans.v2i2.1074
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:cxi:ijans0:v:2:y:2024:i:2:id:1074. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Editorial Team (email available below). General contact details of provider: https://bluemarkpublishers.com/index.php/IJANS .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.