Automated sharing of high-risk IOC's with trusted partners
On this page
Automated sharing of high-risk IOC’s with trusted partners
Learn how to automate sharing of high-risk IOC’s with trusted partners.
Before you begin
Role required:
-
System Administrator (view, create or edit)
-
sn_sec_tisc.admin (view)
About this task
Automated sharing of high-risk IOC’s with trusted partners triggers only when:
-
the type of the observable is a domain name, IPv4 address, or IPv6 address.
-
the observable is in a processed state.
Procedure
-
Navigate to All > Threat Intelligence Security Center > Administration.
-
Select Automated Flows.
-
Select Automated sharing of high-risk IOC's with trusted partners action link to view the respective rule details in the flow designer.
-
View the flow designer action for the following triggers:
Daily at 12.00.00 Run every day once
-
Actions:
-
Look Up System Property Record and Browse outbound intelligence threshold limit:
Look Up System Property Record where (Name is sn_sec_tisc.shared_intelligence_entity_threshold).
-
IOC type = IP, Domain, Hash; Reputation = Malicious ; confidence >= 80 or Threat Score >=80.
Look Up Observable Records where (Type is IP address (V4), or Type is IP address (V6), or Type is Domain Name, or Type is MD5 hash; and Confidence greater than 80, and Reputation is Malicious, and Processing Status is Processed, and Updated on Yesterday) IOC type = IP, Domain, Hash; Reputation = Malicious ; confidence >= 80 or Threat Score >=80.
-
-
If the Threshold of records that can be added to outbound intelligence record is met, then:
-
The system automatically passes the records to the Automated Outbound Intelligence action for processing.
-
End the flow for this sharing of high-risk IOCs with trusted partners.
-
-
If the record count is greater than 0 then the system will process the remaining records.
Example:
If the defined threshold limit is 1000 and a total of 2030 records are to be processed:
-
Outbound Intelligence Record #1 is created with the first 1000 records.
-
Outbound Intelligence Record #2 is created with the next 1000 records.
-
Outbound Intelligence Record #3 is created with the remaining 30 records. This batching process ensures the threshold limit is respected while still processing all the intelligence records efficiently.
-
-
End the flow for this sharing of high-risk IOCs with trusted partners.
[Omitted image "tisc-automated-intel-share.png"] Alt text: Automated IOC Enrichment in TISC.
Parent Topic:Working with automated flows
Related topics
{Automated IOC Enrichment}[]
{Automatically add threat intelligence to a TAXII collection}[]
{Create vulnerability assessment for zero day}[]
{Analyze, assess, and disseminate observables}[]
{Analyze and assess threat IoC’s}[]
{Vulnerability Management Support}[]
{Zero-day vulnerability tracking}[]
{Automatic Threat Actor priority tagging}[]
{Automated flows tables}[]
Keep exploring.
Find another answer, or bring this documentation into your own tools.