| {"title": "What are Expel alerts?", "url": "https://support.expel.io/hc/en-us/articles/12925742896787-What-are-Expel-alerts-", "date": "2023-01-10T21:54:24Z", "contents": "Expel alerts are vendor alerts that appear in Workbench for analysts to\ntriage, investigate, and respond to. An Expel alert is created when one or\nmore vendor alerts satisfy the rule logic in our detection engines. You can\nview Expel alerts on the Alerts analysis dashboard.\n\nEach Expel alert is assigned a severity, which may not always match the\nseverity of the originating vendor alert(s). Expel alerts are _de facto_ tier\n1 when mapping back to the traditional security operations center (SOC)\nprocess. New Expel alerts trigger Ruxie, our automated workflow bot. Ruxie\ncreates new investigative actions, looks for similar Expel alerts, and even\ncloses the alert in certain circumstances.\n\nAs our SOC analysts and Ruxie triage Expel alerts, they can end up proceeding\nin 3 different ways:\n\n * **Closed** : Expel alerts are closed if the vendor alert is benign or doesn’t fall into a category we can investigate further. For example, potentially unwanted programs (PUP) or potentially unwanted applications (PUA).\n\n * **Escalated to investigation** : if there’s a potential of malicious behavior or our SOC analysts need more information, we create an investigation from that Expel alert.\n\n * **Escalated to incident** : if an Expel alert is explicitly malicious, it is immediately escalated to an incident.\n\nIn the case of phishing Expel alerts, instead of a vendor alert being both the\nsource/cause of the Expel alert, it’s a phishing submission.\n\nIn the Expel alert/triage phase Ruxie may contact your organization to ask\n“did you expect this?”.\n\nIn both cases, Expel alerts are closed with a reason and a comment if they are\ndetermined to be benign in nature.\n\n"} |