IBM QRadar SOAR

IBM QRadar

Join this online topic group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#Security
#QRadar
#SecuringhybridcloudandAI
 View Only
  • 1.  Custom Trheat Service

    Posted 06/14/19 08:21 AM
    Hello,

    I want a Custom Threat Service to be triggered only for 'Email Sender' Artifacts. According to documentation and examples, I should add the type 'email.header.sender_address' on the handler but is not working (similarly to 'email.header.to' is for 'Email Recipient' Artifacts). As a workaround I can use 'email.header' but then the CTS is being executed for 'Email Sender' and 'Email Subject' Artifacts (and the Intel Source that I am querying does not support searches for indicators of 'Email Subject' type).

    Was the artifact type 'email.header.sender_address' replaced for another?


    Thanks in advance,

    Dídac Cornet.

    ------------------------------
    Didac Cornet
    ------------------------------


  • 2.  RE: Custom Trheat Service

    Posted 09/09/19 01:08 AM
    According to the guide, 'Email Sender' and 'Email Subject' has both same Name : 'email.header' apart from our acceptance.

    The following is the results on my Resilient V33 environment by capturing network traffic.
    type value JSON representation in network capture
    Email Sender test01@example.com {"type":"email.header","value":"test01@example.com"}
    Email Sender Name test01 {"type":"email.header.sender_name","value":"test01"}
    Email Subject test01_subject {"type":"email.header","value":"test01_subject"}
    Email Receipient test01@example.com, test02@example.com {"type":"email.header.to","value":"test02@example.com"}
    Email Body test01_body {"type":"email.body","value":"test01_body"}
    Email Attachment Name test01_attachment {"type":"file.name","value":"test01_attachment"}

    With the guide, I found a typo that property type latlng (p12) was actually lat_lng instead. So I also would like to know what's are really expected.

    ------------------------------
    Yohji Amano
    ------------------------------



  • 3.  RE: Custom Trheat Service

    Posted 09/09/19 06:56 PM

    Hello Yohji and Dídac,

    Dídac email.header is what you're looking for to trigger all Email Sender Name Artifacts (Name of suspicious email sender) or Email Subject Artifacts (Suspicious email subject). email.header.sender_address will trigger all Email Sender Address Artifacts (Suspicious email sender). If it's an email address that you're trying to scan you'll need to use Email Sender Address Artifact and use email.header.sender_address for the handler.

    Yohji I just skimmed the CTS guide and I think the typo you're referring to is in Chapter 6 Data Structures under ArtifactPropertyDTO? You're right it should be lat_lng property type, thank you for informing us of the typo. We'll make a correction and update the guide.

    Please let us know if you have any more questions.

    Cheers,
    Tamara Zlender



    ------------------------------
    Tamara Zlender
    ------------------------------



  • 4.  RE: Custom Trheat Service

    Posted 09/11/19 01:03 AM
    Hello Tamara. Thank you for your response.

    I still have a question.

    According to the table of 'Email artifact types' in the CTS guide, 'Email Sender Address' is listed as display name to send  the name: 'email.header.sender_address' .

    On the other hand, 'Email Sender Address' is not in the Artifact list. So I think Resilient will not send 'email.header.sender_address'  to CTS URL.
    From Artifact tab in an incident Resilient Web Page

    It seemed to me that there are some differences between the artifact list in Resilient web page and the list related to Email artifacts in CTS guide


    ------------------------------
    Yohji Amano
    ------------------------------



  • 5.  RE: Custom Trheat Service

    Posted 09/11/19 10:29 AM
    Hello Yohji,

    I see the problem. I cannot locate Email Sender Address in the product as well. I'm very sorry for the confusion.
    I will need to investigate this and will get back to you as soon as I find an answer.

    Tamara

    ------------------------------
    Tamara Zlender
    ------------------------------



  • 6.  RE: Custom Trheat Service

    Posted 09/13/19 03:27 PM

    Hello Yohji and Dídac,

    I was able to confirm 'Email Sender Address' is not a valid Artifact Type, email.header.sender_address isn't available to use. This is bug in our documentation. We will update the documentation with our next release. I apologize for the confusion.

    You could use 'Email Sender' and email.header to scan an email address with a CTS. Having said that I understand CTS is being executed for both 'Email Sender' and 'Email Subject' Artifacts Types and that in your use case this isn't a desired outcome.
    At the moment I don't think there is a good way to filter them in Python code, CTS only knows about artifact's value and type. You could theoretically check the value if it includes an '@' character but this might not be a solution you were hoping for.
    Also this sounds like a good idea to post at Resilient Ideas (RFEs) https://success.resilientsystems.com/hc/en-us/articles/360000627425-Ideas-formerly-RFEs

    Best,
    Tamara Zlender



    ------------------------------
    Tamara Zlender
    ------------------------------



  • 7.  RE: Custom Trheat Service

    Posted 09/14/19 03:38 PM
    Hi Tamara, thank you for your understandings and recommendations.

    I hope 'Email Sender' and 'Email Subject' Artifacts Types are identifiable in the future release.

    ------------------------------
    Yohji Amano
    ------------------------------