Getting Data In

Getting Data into the Splunk Add-On for Microsoft Security

qzy
Observer

Hi folks,

I am trying to get Defender logs into the  Splunk Add-On for Microsoft Security but I am struggling a bit.

It "appears" to be configured correctly but I am seeing this error in the logs:
ERROR pid=222717 tid=MainThread file=ms_security_utils.py:get_atp_alerts_odata:261 | Exception occurred while getting data using access token : HTTPSConnectionPool(host='api.securitycenter.microsoft.com', port=443): Max retries exceeded with url: /api/alerts?$expand=evidence&$filter=lastUpdateTime+gt+2024-05-22T12:34:35Z (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7fe514fa1bd0>, 'Connection to api.securitycenter.microsoft.com timed out. (connect timeout=60)'))

Is this an issue with the way the Azure Connector App is permissioned or something else entirely?

Thanks in advance

Labels (2)
0 Karma

qzy
Observer

Thank you for the response, and it was indeed a Firewall Rule issue! 

I also had to ensure these permissions were granted on the Azure side....
SecurityIncident.Read.all/SecurityIncident.ReadWrite.all 
Incident.Read.All/Incident.ReadWrite.All

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Connection timeout means that your end tried to establish connection with the destinations server (api.securityserver.microsoft.com) but didn't get any response. This typically means network-level problems (like lack of proper firewall rules allowing outgoing traffic) or (actually it's the same thing but pushed one step further) not configured proxy server when direct outgoing traffic is forbidden.

Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...