%3CLINGO-SUB%20id%3D%22lingo-sub-2102043%22%20slang%3D%22en-US%22%3EMigrating%20QRadar%20offenses%20to%20Azure%20Sentinel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2102043%22%20slang%3D%22en-US%22%3E%3CH2%20id%3D%22toc-hId--1301738137%22%20id%3D%22toc-hId--527023215%22%3E%3CSTRONG%3EHow%20do%20you%20export%20QRadar%20offenses%20to%20Azure%20Sentinel%3F%3C%2FSTRONG%3E%3C%2FH2%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3ESpecial%20thanks%20to%26nbsp%3B%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F49603%22%20target%3D%22_blank%22%3E%3CEM%3E%40Hesham%20Saad%3C%2FEM%3E%3C%2FA%3E%3CEM%3E%26nbsp%3Bfrom%20our%20Cybersecurity%20Technical%20Solutions%20Specialist%26nbsp%3Bteam%26nbsp%3Bfor%20collaborating%20on%20this%20blog%20post%20with%20me!%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECustomers%20are%20frequently%20inquiring%20on%20how%20to%20migrate%20smoothly%20from%20their%20current%20SIEM%20solution%20to%20Azure%20Sentinel.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20couple%20of%20weeks%20ago%2C%20we%20started%20with%20a%20solution%20to%20export%20data%20from%20Splunk%20to%20Azure%20Sentinel.%20Highly%20recommended%20to%20check%20out%20the%20blog%20post%20by%20our%20colleague%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F695548%22%20target%3D%22_blank%22%3E%40yokhaldi%3C%2FA%3E%26nbsp%3B(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sentinel%2Fhow-to-export-data-from-splunk-to-azure-sentinel%2Fba-p%2F1891237%22%20target%3D%22_blank%22%3EHow%20to%20export%20data%20from%20Splunk%20to%20Azure%20Sentinel%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sentinel%2Fhow-to-export-data-from-splunk-to-azure-sentinel%2Fba-p%2F1891237%22%20target%3D%22_blank%22%3E)%3C%2FA%3E%2C%20a%20logical%20sequence%20to%20his%20blog%20post%20is%20a%20walk-through%20explaining%20how%20to%20consume%20security%20telemetry%20data%20directly%20%3CSTRONG%3Efrom%26nbsp%3BQRadar%20to%20Azure%20Sentinel%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOne%20of%20the%20key%20challenges%20in%20migrating%20to%20another%20SIEM%20is%20the%20intermediate%20phase.%20In%20this%20phase%2C%20both%20SIEMs%20are%20running%20side%20by%20side%20until%20the%20migration%20is%20complete.%20To%20keep%20a%20good%20overview%20(single%20pane%20of%20glass)%20of%20all%20the%20incidents%20in%20your%20deployment%20from%20both%20SIEMs%2C%20it%20is%20of%20utmost%20importance%20to%20have%20all%20your%20alerts%20and%20incidents%20in%20one%20place.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EThis%20blogpost%20will%20describe%20how%20you%20can%20forward%20all%20your%20QRadar%20offenses%20to%20your%20Azure%20Sentinel%20environment%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3ELet%E2%80%99s%20get%20started!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20highlighted%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239761%22%20target%3D%22_blank%22%3E%40Alp%20Babayigit%3C%2FA%3E%E2%80%99s%20post%20%22%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sentinel%2Fazure-sentinel-side-by-side-with-qradar%2Fba-p%2F1488333%22%20target%3D%22_blank%22%3EAzure%20Sentinel%20Side-by-Side%20with%20QRadar%22%3C%2FA%3E%2C%26nbsp%3Bthere%20are%20many%20reasons%20why%20enterprises%20are%20using%20multiple%20SIEM%20products%20simultaneously.%26nbsp%3BYou%20can%20use%20various%20SIEM%20solutions%20at%20once%20as%20a%20permanent%20measure%2C%20for%20example%2C%20to%20correlate%20with%20available%20data%20sources%26nbsp%3Bwhile%20using%20Azure%20Sentinel%26nbsp%3Bas%20the%20single%20pane%20of%20glass%20to%20centralize%20all%20incidents).%20However%2C%20most%20of%20the%20time%2C%20the%20side-by-side%20architecture%20is%20used%26nbsp%3Bduring%20a%20transition%20period%26nbsp%3Bfor%26nbsp%3Bmigrating%20from%20one%20SIEM%20to%20our%20SIEM%20and%20SOAR%26nbsp%3Bsolution%2C%20Azure%20Sentinel.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhy%20do%20so%20many%20enterprises%20transition%20to%20Azure%20Sentinel%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EThe%20current%20trend%20in%20many%20businesses%20is%20the%20consumption%20of%20more%20and%20more%20cloud%20services%2C%20hence%20the%20huge%20ask%20for%26nbsp%3Bcloud-native%26nbsp%3BSIEMs.%20This%20is%20where%20Azure%20Sentinel%20comes%26nbsp%3Bto%20the%20rescue%26nbsp%3Bwith%20the%20following%20advantages%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EEasy%20collection%20from%20cloud%20sources%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EEffortless%20infinite%20scale%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EIntegrated%20automation%20capabilities%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EContinually%20maintained%20cloud%20and%20on-premises%20use%20cases%20enhanced%20with%20Microsoft%20TI%20(Threat%20Intelligence)%20and%20ML%20(Machine%20Learning)%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EGithub%26nbsp%3Bcommunity%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EMicrosoft%20research%20and%20ML%20capabilities%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EAvoid%20sending%20cloud%20telemetry%20downstream%20(send%20cloud%20data%20to%26nbsp%3Bon-premise%26nbsp%3BSIEM)%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThere%20are%20several%20best%20practice%20integration%20options%20to%20operate%20Azure%20Sentinel%20Side-by-Side%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EAlerts%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EEvents%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EUpstream%20to%20Azure%20Sentinel%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3ECEF%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogstash%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogic%20Apps%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAPI%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3ECEF%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogstash%26nbsp%3B%3CBR%20%2F%3EAPI%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EDownstream%20from%20Azure%20Sentinel%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3ESecurity%20Graph%20Security%20API%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPowershell%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELogic%20Apps%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAPI%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3EAPI%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPowershell%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20blog%20post%20will%20explain%20how%20to%20ingest%26nbsp%3BQRadar%26nbsp%3Boffense%20data%20into%20an%20Azure%20Sentinel%20workspace.%26nbsp%3BThe%20solution%20will%20use%20the%20QRadar%20API%20and%20can%20be%20adapted%20to%20query%20event%20data%20from%20the%26nbsp%3BQRadar%26nbsp%3Bevent%20logs.%20That%20said%2C%20there%20is%20another%20solution%20for%20ingesting%26nbsp%3BQRadar%26nbsp%3Bevent%26nbsp%3Blog%20data%3A%20use%20routing%20rules%20and%20forwarding%20destinations%26nbsp%3Bin%26nbsp%3BQRadar.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--611176663%22%20id%3D%22toc-hId-163538259%22%3EScenario%20description%26nbsp%3B%3C%2FH3%3E%0A%3CP%3EAs%26nbsp%3Bmentioned%2C%20this%20blog%20post%20will%20focus%20on%20getting%20offenses%20from%26nbsp%3BQRadar%26nbsp%3Binto%20Azure%20Sentinel%26nbsp%3Bas%20our%20primary%20SIEM.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20two%20routes%20we%20can%20take%20to%20get%20offense%20data%26nbsp%3Binto%20Azure%20Sentinel%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EQRadar%26nbsp%3Bcan%20notify%20us%20when%20a%20new%20offense%20is%20created%2C%20and%20as%20a%26nbsp%3Bresponse%2C%26nbsp%3Bwe%20can%20pull%20the%20offense%20data%20into%20our%20log%20analytics%20workspace.%3C%2FLI%3E%0A%3CLI%3EAnother%20route%20is%20to%20schedule%20the%20pulling%20of%20the%20QRadar%20offense%26nbsp%3Bdata.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20this%20blog%20post%2C%20we%20will%20detail%20the%20second%20option's%20implementation%3A%26nbsp%3BLet%E2%80%99s%20assume%20that%20your%20SOC%20team%20wants%20to%20collect%26nbsp%3Boffense%20data%20from%26nbsp%3BQRadar%26nbsp%3Baccording%20to%20a%20specific%20schedule%2Ftimeframe.%26nbsp%3BAzure%20functions%20will%20schedule%20API%20calls%20to%26nbsp%3BQRadar%26nbsp%3Bto%20pull%20the%20desired%20data%20into%20our%26nbsp%3Bworkspace.%26nbsp%3BThe%20response%20format%20when%20requesting%20data%20from%26nbsp%3BQRadar%26nbsp%3Bvia%20the%20API%20is%20in%26nbsp%3BJSON.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20following%20guide%20will%20explain%20the%20process%20step%20by%20step.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-79384811%22%20id%3D%22toc-hId-854099733%22%3E%3CSTRONG%3EOnboard%20Azure%20Sentinel%26nbsp%3B%3C%2FSTRONG%3E%3C%2FH4%3E%0A%3CP%3EWe%20assume%20the%20onboarding%20Azure%20Sentinel%20is%20completed.%26nbsp%3B%3CBR%20%2F%3EIf%20not%3B%26nbsp%3BI%20would%20like%20to%20forward%20you%20to%20the%20following%20links%20for%26nbsp%3Ba%26nbsp%3Bquickstart%26nbsp%3Bon%20onboarding%20Azure%20Sentinel%3A%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fquickstart-onboard%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EQuickstart%3A%20On-board%20Azure%20Sentinel%3C%2FA%3E%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fquickstart-get-visibility%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EQuickstart%3A%20Get%20started%20with%20Azure%20Sentinel%26nbsp%3B%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CH4%20id%3D%22toc-hId--1728069652%22%20id%3D%22toc-hId--953354730%22%3EQRadar%26nbsp%3Benvironment%20configuration%26nbsp%3B%3C%2FH4%3E%0A%3CP%3EWe%20also%20assume%20that%20you%20have%20an%20up%20and%20running%26nbsp%3BQRadar%26nbsp%3Benvironment.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E(For%20those%20who%20want%20to%20replicate%20this%20walkthrough%20in%20a%20lab%20environment%2C%26nbsp%3Bhere%20is%20a%20guide%26nbsp%3Bon%20how%20to%20install%26nbsp%3BQRadar%26nbsp%3Bin%20Azure%3A%26nbsp%3B%3C%2FEM%3E%3CA%20href%3D%22https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2FSS42VS_7.3.3%2Fcom.ibm.qradar.doc%2Ft_Cloud_Install_Qradar_Azure.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CEM%3EConfiguring%20a%20Console%20on%20Microsoft%20Azure%20(IBM)%3C%2FEM%3E%3C%2FA%3E%3CEM%3E%26nbsp%3B)%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20accomplish%20the%20exporting%20of%20offense%20data%20from%20QRadar%2C%20we%20will%20invoke%20GET%20requests%20from%20the%20QRadar%20API.%26nbsp%3BYou%20will%20need%20an%26nbsp%3Bauthentication%20token%20to%20authenticate%20the%20API%20calls%20that%20the%26nbsp%3BAzure%20Function%20will%26nbsp%3Bmake.%20To%20create%20an%20authentication%20token%20in%20QRadar%2C%20go%20to%26nbsp%3Bthe%20%E2%80%9CManage%20Authorized%20Services%E2%80%9D%20window%20and%20create%20a%20new%20token.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_1-1612787161878.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253235i3C7636785DA161A9%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_1-1612787161878.png%22%20alt%3D%22NChristis_1-1612787161878.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20also%20have%20to%20make%20sure%20the%20Azure%20Function%20(which%20we%20will%20create%20in%20a%20couple%20of%20steps)%20has%20HTTP%20access%20to%20the%20QRadar%20system%20to%20make%20the%20API%20calls.%20A%20guide%20on%20how%20to%20determine%20which%20IP%20addresses%20will%20be%20used%20by%20your%20Azure%20Function%20can%20be%20found%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-functions%2Fip-addresses%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%E2%80%99s%20walk-through%20which%20QRadar%20API%20calls%20we%20used%20for%20this%20blogpost%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUse%20your%26nbsp%3B%3CEM%3Ehttps%3A%2F%2F%3CMANAGEMENT_IP%3E%2Fapi_doc%3C%2FMANAGEMENT_IP%3E%3C%2FEM%3E%26nbsp%3Blink%26nbsp%3Bto%20get%20to%26nbsp%3Bthe%20interactive%26nbsp%3BQRadar%26nbsp%3BAPI%20documentation%20to%20access%20technical%20details%20for%20the%26nbsp%3BQRadar%26nbsp%3BRESTful%20API%20and%20then%20look%20under%26nbsp%3B%3CEM%3E%2Fsiem%2Foffenses%3C%2FEM%3E%26nbsp%3Bfor%20our%20get%20request%20for%20the%20offense%20data%3A%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_2-1612787161882.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253234i747E652666989803%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_2-1612787161882.png%22%20alt%3D%22NChristis_2-1612787161882.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20following%20screenshot%2C%20you%20can%20see%20which%20fields%20you%20can%20filter%20on%20in%20your%20GET%20request%20or%20specify%20the%20fields%20you%20want%20to%20retrieve%20as%20a%20response.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20blog%20post%20will%20not%20specify%20specific%20fields%20to%20retrieve%3B%20we%20will%20retrieve%20them%20all.%26nbsp%3BWe%20will%2C%20however%2C%20set%20a%20filter%26nbsp%3Bparameter%20in%20the%20API%20calls.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_3-1612787161891.jpeg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253236i1146F2EF13CFB0D5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_3-1612787161891.jpeg%22%20alt%3D%22NChristis_3-1612787161891.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20we%20previously%20mentioned%2C%20we%20will%26nbsp%3Bschedule%26nbsp%3Brequests%20to%20get%26nbsp%3Bthe%20offenses%20from%20QRadar%26nbsp%3Binto%20our%20Azure%20Sentinel%20environment.%26nbsp%3BTo%20make%20it%20more%20efficient%26nbsp%3B(less%20data%20overhead)%2C%20we%20will%20only%20ask%20for%20the%20offenses%20generated%20since%20the%20last%20scheduled%20request.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EFor%20example%2C%20we%20will%20schedule%20our%20Azure%20Function%20to%20perform%26nbsp%3Ban%26nbsp%3BAPI%20request%20every%2024%20hours%2C%20and%20we%20will%20only%20retrieve%20the%20offenses%20created%20in%20the%20last%2024%20hours%20in%20QRadar.%3C%2FP%3E%0A%3CP%3EWe%26nbsp%3Bwill%20filter%20on%26nbsp%3B%3CEM%3Estart_time%3C%2FEM%3E%3A%20%22The%20number%20of%20milliseconds%20since%20epoch%20when%20the%20offense%20was%20started%22.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E(Side%20note%3A%20you%20can%20also%20change%20the%20code%20to%20retrieve%20the%20offenses%20updated%20in%20the%20last%2024%20hours%3B%20you%20need%20to%20filter%20on%26nbsp%3B%3CEM%3Elast_updated_time%3C%2FEM%3E%26nbsp%3Bin%20the%20API%20request%20instead%20of%26nbsp%3B%3CEM%3Estart_time%3C%2FEM%3E).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-759443181%22%20id%3D%22toc-hId-1534158103%22%3EPowerShell%26nbsp%3Bcode%26nbsp%3B%3C%2FH4%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20export%20offense%20data%20from%26nbsp%3BQRadar%26nbsp%3Band%26nbsp%3Bimport%20it%20into%20Azure%20Sentinel%2C%20we%20create%20a%20scheduled%20Azure%20Function%20invoking%20a%20GET%20request%26nbsp%3Bto%26nbsp%3Bthe%26nbsp%3BQRadar%26nbsp%3BAPI%20via%26nbsp%3BPowerShell%20code.%3C%2FP%3E%0A%3CP%3EIn%20the%26nbsp%3BPowerShell%26nbsp%3Bcode%2C%20we%20will%20perform%20the%20following%20steps%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFirst%2C%20specify%20all%20the%20required%20inputs%3A%3C%2FLI%3E%0A%3CUL%3E%0A%3CLI%3EQRadars%20management%20ip%3C%2FLI%3E%0A%3CLI%3EQRadar%20authentication%20token%3C%2FLI%3E%0A%3CLI%3EAzure%20Sentinel%20workspace%20id%20and%20shared%20key%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CLI%3ETrust%20the%20certificate%20of%26nbsp%3BQRadar%26nbsp%3B%2F%20ignore%20the%26nbsp%3Bcertificate.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3Eif%20(%22TrustAllCertsPolicy%22%20-as%20%5Btype%5D)%20%7B%7D%20else%20%7B%20%0A%20%20%20%20%20%20%20%20Add-Type%20%22using%20System.Net%3Busing%20System.Security.Cryptography.X509Certificates%3Bpublic%20class%20TrustAllCertsPolicy%20%3A%20ICertificatePolicy%20%7Bpublic%20bool%20CheckValidationResult(ServicePoint%20srvPoint%2C%20X509Certificate%20certificate%2C%20WebRequest%20request%2C%20int%20certificateProblem)%20%7Breturn%20true%3B%7D%7D%22%20%0A%20%20%20%20%20%20%20%20%5BSystem.Net.ServicePointManager%5D%3A%3ACertificatePolicy%20%3D%20New-Object%20TrustAllCertsPolicy%20%0A%7D%20%0ASet-ExecutionPolicy%20-Scope%20Process%20-ExecutionPolicy%20Bypass%20%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECalculate%20the%20number%20of%20milliseconds%20since%20epoch%20when%20the%20offense%20was%26nbsp%3Bstarted%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ECreate%20the%26nbsp%3BAPI%26nbsp%3Bcall%20to%26nbsp%3BQRadar%26nbsp%3Bto%20get%20all%20the%20offenses.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-powershell%22%3E%3CCODE%3E%24headers%20%3D%20%40%7B%7D%20%0A%24headers.add(%22Version%22%2C%2212.0%22)%20%0A%24headers.add(%22Content-Type%22%2C%22application%2FJSON%22)%20%0A%24Headers.add(%22SEC%22%2C%24token)%20%0A%24url%20%3D%20%22%22https%3A%2F%2F%22%20%2B%20%24consoleIP%20%2B%20%22%2Fapi%2Fsiem%2Foffenses%3Ffilter%3Dstart_time%253E%22%20%2B%20%24unixTime%20%0A%24OffenseInfo%20%3D%20Invoke-RestMethod%20-Method%20GET%20-Headers%20%24headers%20-Uri%20%24url%20%20%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ETranslate%20the%20received%20JSON%20response%20from%26nbsp%3BQRadar%26nbsp%3Bto%20JSON%20allowed%20input%20for%20the%20Azure%20Sentinel%20API%20call%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ESend%20the%20translated%20JSON%20information%20via%26nbsp%3BAPI%20call%20to%20Azure%20Sentinel.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20data-unlink%3D%22true%22%3EYou%20can%20find%20the%20complete%20script%20code%20on%26nbsp%3B%3CA%20title%3D%22Github%22%20href%3D%22https%3A%2F%2Fgithub.com%2FNchristis%2FQRadarToSentinel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGithub.%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--1048011282%22%20id%3D%22toc-hId--273296360%22%3EAzure%20Function%26nbsp%3B%3C%2FH4%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20last%20step%20in%20this%20whole%20procedure%20is%20to%20run%20the%26nbsp%3BPowerShell%26nbsp%3Bscript%20in%20an%20Azure%20Function%20that%20will%20run%20on%20a%20schedule%20and%20push%20the%20QRadar%20offense%20data%20into%20our%20Azure%20Sentinel%20workspace.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20the%20following%20screenshot%2C%20you%20can%20see%20the%20configuration%20of%20the%20Azure%20Function%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22QradaroffensestoSentinel.gif%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253242iB0560ED326DF5255%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22QradaroffensestoSentinel.gif%22%20alt%3D%22QradaroffensestoSentinel.gif%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%E2%80%83%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId-1439501551%22%20id%3D%22toc-hId--2080750823%22%3ELogs%20in%20Azure%20Sentinel%26nbsp%3B%26nbsp%3B%3C%2FH4%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20logs%26nbsp%3Bwill%20go%20to%20a%20custom%20Azure%20Sentinel%20table%26nbsp%3B%E2%80%98QRadar_Offense_CL%E2%80%99%26nbsp%3B(if%20you%20specified%20the%20table%20as%26nbsp%3BQRadar_Offense%26nbsp%3Blike%20in%20our%20code)%26nbsp%3Bas%20shown%20in%20the%20screenshot%20below.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_5-1612787162032.jpeg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253237i66B9917FA2D03A6B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_5-1612787162032.jpeg%22%20alt%3D%22NChristis_5-1612787162032.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20this%20example%20corresponds%20to%20the%20following%20fictional%20offense%20in%26nbsp%3BQRadar%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_6-1612787162039.jpeg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253240iD5B49BCD9858162C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_6-1612787162039.jpeg%22%20alt%3D%22NChristis_6-1612787162039.jpeg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH4%20id%3D%22toc-hId--367952912%22%20id%3D%22toc-hId-406762010%22%3EDeploy%20this%20solution%20to%20your%20environment%3C%2FH4%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAn%20ARM%20template%20to%20automate%20the%20onboarding%20of%20the%20Azure%20Function%20can%20be%20found%20on%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FNchristis%2FSentinelProjects-Scripts%2Ftree%2Fmain%2FArm%2520templates%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EGithub%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22NChristis_7-1612787761070.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F253243i6279F6DCC31A439F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22NChristis_7-1612787761070.png%22%20alt%3D%22NChristis_7-1612787761070.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--378456016%22%20id%3D%22toc-hId-396258906%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22toc-hId-2109056817%22%20id%3D%22toc-hId--1411195557%22%3ESummary%3C%2FH3%3E%0A%3CP%3ETo%20export%20offenses%20from%26nbsp%3BQRadar%26nbsp%3Band%26nbsp%3Bimport%20to%20Azure%20Sentinel%2C%20we%20created%20a%20scheduled%20Azure%20Function%20that%20will%26nbsp%3Binvoke%20a%20GET%20request%26nbsp%3Bto%26nbsp%3Bthe%26nbsp%3BQRadar%26nbsp%3BAPI%20via%26nbsp%3BPowerShell%26nbsp%3Band%20push%20the%20data%20into%20your%20Azure%20Sentinel%20workspace.%20We%20encourage%20you%20to%20try%20it%20yourself%20and%20leverage%20the%20next%20generation%20of%20SIEM%20%26nbsp%3Bfor%20your%20environment.%26nbsp%3B%26nbsp%3BYou%20can%20also%20contribute%20your%20new%20connectors%2C%20workbooks%2C%20analytics%2C%20and%20more%20in%20Azure%20Sentinel.%20Get%20started%20now%20by%20joining%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fthreathunters%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAzure%20Sentinel%20Threat%20Hunters%20GitHub%20community%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2102043%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22TextRun%20%20BCX9%20SCXW18653240%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX9%20SCXW18653240%22%3EThis%20blog%20post%20will%20explain%20how%20to%20ingest%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22TextRun%20%20BCX9%20SCXW18653240%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22SpellingError%20%20BCX9%20SCXW18653240%22%3EQRadar%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22TextRun%20%20BCX9%20SCXW18653240%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX9%20SCXW18653240%22%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eoffense%20data%20into%20the%20Azure%20Sentinel%20workspace.%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22TextRun%20%20BCX9%20SCXW18653240%22%20data-contrast%3D%22auto%22%3E%3CSPAN%20class%3D%22NormalTextRun%20%20BCX9%20SCXW18653240%22%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2102043%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Sentinel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQRadar%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESIEM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

How do you export QRadar offenses to Azure Sentinel?

 

Special thanks to @Hesham Saad from our Cybersecurity Technical Solutions Specialist team for collaborating on this blog post with me! 

 

Customers are frequently inquiring on how to migrate smoothly from their current SIEM solution to Azure Sentinel.

 

A couple of weeks ago, we started with a solution to export data from Splunk to Azure Sentinel. Highly recommended to check out the blog post by our colleague @yokhaldi (How to export data from Splunk to Azure Sentinel), a logical sequence to his blog post is a walk-through explaining how to consume security telemetry data directly from QRadar to Azure Sentinel.

 

One of the key challenges in migrating to another SIEM is the intermediate phase. In this phase, both SIEMs are running side by side until the migration is complete. To keep a good overview (single pane of glass) of all the incidents in your deployment from both SIEMs, it is of utmost importance to have all your alerts and incidents in one place.

 

This blogpost will describe how you can forward all your QRadar offenses to your Azure Sentinel environment.


Let’s get started! 

 

As highlighted in @Alp Babayigit’s post "Azure Sentinel Side-by-Side with QRadar", there are many reasons why enterprises are using multiple SIEM products simultaneously. You can use various SIEM solutions at once as a permanent measure, for example, to correlate with available data sources while using Azure Sentinel as the single pane of glass to centralize all incidents). However, most of the time, the side-by-side architecture is used during a transition period for migrating from one SIEM to our SIEM and SOAR solution, Azure Sentinel. 

 

Why do so many enterprises transition to Azure Sentinel? 


The current trend in many businesses is the consumption of more and more cloud services, hence the huge ask for cloud-native SIEMs. This is where Azure Sentinel comes to the rescue with the following advantages: 

 

  • Easy collection from cloud sources 
  • Effortless infinite scale 
  • Integrated automation capabilities 
  • Continually maintained cloud and on-premises use cases enhanced with Microsoft TI (Threat Intelligence) and ML (Machine Learning) 
  • Github community 
  • Microsoft research and ML capabilities 
  • Avoid sending cloud telemetry downstream (send cloud data to on-premise SIEM)  

There are several best practice integration options to operate Azure Sentinel Side-by-Side:

 

 

Alerts 

Events 

Upstream to Azure Sentinel 

CEF 

Logstash 

Logic Apps 

API

CEF 

Logstash 
API 

Downstream from Azure Sentinel 

Security Graph Security API  

Powershell 

Logic Apps 

API 

API  

Powershell 

 

This blog post will explain how to ingest QRadar offense data into an Azure Sentinel workspace. The solution will use the QRadar API and can be adapted to query event data from the QRadar event logs. That said, there is another solution for ingesting QRadar event log data: use routing rules and forwarding destinations in QRadar. 

 

Scenario description 

As mentioned, this blog post will focus on getting offenses from QRadar into Azure Sentinel as our primary SIEM. 

 

There are two routes we can take to get offense data into Azure Sentinel:

 

  • QRadar can notify us when a new offense is created, and as a response, we can pull the offense data into our log analytics workspace.
  • Another route is to schedule the pulling of the QRadar offense data. 

 

In this blog post, we will detail the second option's implementation: Let’s assume that your SOC team wants to collect offense data from QRadar according to a specific schedule/timeframe. Azure functions will schedule API calls to QRadar to pull the desired data into our workspace. The response format when requesting data from QRadar via the API is in JSON. 

 

The following guide will explain the process step by step. 

 

Onboard Azure Sentinel 

We assume the onboarding Azure Sentinel is completed. 
If not; I would like to forward you to the following links for a quickstart on onboarding Azure Sentinel: 

QRadar environment configuration 

We also assume that you have an up and running QRadar environment. 

(For those who want to replicate this walkthrough in a lab environment, here is a guide on how to install QRadar in Azure: Configuring a Console on Microsoft Azure (IBM) )

 

To accomplish the exporting of offense data from QRadar, we will invoke GET requests from the QRadar API. You will need an authentication token to authenticate the API calls that the Azure Function will make. To create an authentication token in QRadar, go to the “Manage Authorized Services” window and create a new token.

 

NChristis_1-1612787161878.png

 

 

You also have to make sure the Azure Function (which we will create in a couple of steps) has HTTP access to the QRadar system to make the API calls. A guide on how to determine which IP addresses will be used by your Azure Function can be found here.

 

Let’s walk-through which QRadar API calls we used for this blogpost: 

 

Use your https://<management_ip>/api_doc link to get to the interactive QRadar API documentation to access technical details for the QRadar RESTful API and then look under /siem/offenses for our get request for the offense data: 


NChristis_2-1612787161882.png

 

 

In the following screenshot, you can see which fields you can filter on in your GET request or specify the fields you want to retrieve as a response. 

This blog post will not specify specific fields to retrieve; we will retrieve them all. We will, however, set a filter parameter in the API calls.


NChristis_3-1612787161891.jpeg

 

As we previously mentioned, we will schedule requests to get the offenses from QRadar into our Azure Sentinel environment. To make it more efficient (less data overhead), we will only ask for the offenses generated since the last scheduled request.  


For example, we will schedule our Azure Function to perform an API request every 24 hours, and we will only retrieve the offenses created in the last 24 hours in QRadar.

We will filter on start_time: "The number of milliseconds since epoch when the offense was started". 

(Side note: you can also change the code to retrieve the offenses updated in the last 24 hours; you need to filter on last_updated_time in the API request instead of start_time). 

 

PowerShell code 

 

To export offense data from QRadar and import it into Azure Sentinel, we create a scheduled Azure Function invoking a GET request to the QRadar API via PowerShell code.

In the PowerShell code, we will perform the following steps: 

 

  • First, specify all the required inputs:
    • QRadars management ip
    • QRadar authentication token
    • Azure Sentinel workspace id and shared key
  • Trust the certificate of QRadar / ignore the certificate. 

 

if ("TrustAllCertsPolicy" -as [type]) {} else { 
        Add-Type "using System.Net;using System.Security.Cryptography.X509Certificates;public class TrustAllCertsPolicy : ICertificatePolicy {public bool CheckValidationResult(ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) {return true;}}" 
        [System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy 
} 
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass 

 

  • Calculate the number of milliseconds since epoch when the offense was started 
  • Create the API call to QRadar to get all the offenses.  

 

$headers = @{} 
$headers.add("Version","12.0") 
$headers.add("Content-Type","application/JSON") 
$Headers.add("SEC",$token) 
$url = ""https://" + $consoleIP + "/api/siem/offenses?filter=start_time%3E" + $unixTime 
$OffenseInfo = Invoke-RestMethod -Method GET -Headers $headers -Uri $url  

 

  • Translate the received JSON response from QRadar to JSON allowed input for the Azure Sentinel API call 
  • Send the translated JSON information via API call to Azure Sentinel. 

You can find the complete script code on Github. 

 

Azure Function 

 

The last step in this whole procedure is to run the PowerShell script in an Azure Function that will run on a schedule and push the QRadar offense data into our Azure Sentinel workspace.

 

In the following screenshot, you can see the configuration of the Azure Function: 

 

QradaroffensestoSentinel.gif

 

Logs in Azure Sentinel  

 

The logs will go to a custom Azure Sentinel table ‘QRadar_Offense_CL’ (if you specified the table as QRadar_Offense like in our code) as shown in the screenshot below. 

 

NChristis_5-1612787162032.jpeg

 

And this example corresponds to the following fictional offense in QRadar: 

 

NChristis_6-1612787162039.jpeg

 

Deploy this solution to your environment

 

An ARM template to automate the onboarding of the Azure Function can be found on Github.

 

NChristis_7-1612787761070.png

 

Summary

To export offenses from QRadar and import to Azure Sentinel, we created a scheduled Azure Function that will invoke a GET request to the QRadar API via PowerShell and push the data into your Azure Sentinel workspace. We encourage you to try it yourself and leverage the next generation of SIEM  for your environment.  You can also contribute your new connectors, workbooks, analytics, and more in Azure Sentinel. Get started now by joining the Azure Sentinel Threat Hunters GitHub community.