Clarification on Fetching Assets via listassets API – Artifact vs Asset

@rohan1804 the difference in artifact and asset are described in the Search API docs A artifact could be an IOC that has been seen in your environment.

Hi @James_E ,

We have ingested logs into Google SecOps using the AWS S3 feeder. The logs are being parsed correctly, and alerts are also being generated as expected.

These logs contain known malicious IPs, each with a threat score above 80, verified via the Mandiant portal. However, despite the alerts being triggered, the corresponding IOCs are not being generated.

We’d like to clarify:

• Is it mandatory to enable Applied Threat Intelligence in order for IOCs to be generated?

• If so, does this feature require the Enterprise Plus edition?

Looking forward to your guidance on this.

Thanks in advance!

@rohan1804 Applied Threat Intelligence  does require Enterprise Plus. You do have the ability to ingest your own supported intel feeds or send in IOC's through the ingestion API. For the logs that you're currently ingesting, the key here is that the IOC's need to be ingested as an entity and not an event.

What log type are you currently ingesting for IOC's?

Hi @James_E ,

We are ingesting AWS Cloudtrail json logs, through a SIEM AWS Cloudtrail feeder below is the sample for your reference:

Hi @James_E ,

Just following up on our earlier message - we’re currently exploring how to generate Assets in the Google SecOps platform, and your guidance would be really helpful at this stage.

Here’s a quick summary of what we’ve tried so far:

• Ingested IoCs and assets as events

• Ingested IoCs and assets as entities

• Ensured the time range of the IoC is within scope

Challenges we’re facing:

• Unable to generate IoCs and assets visibly within the platform

• Receiving empty responses from the legacySearchArtifact endpoint

Our current focus is on successfully generating Assets. If there are any specific formats, ingestion methods, or query parameters we should follow, we’re open to all suggestions.

Looking forward to your inputs. Thank you!

cc: @rohan1804 @vishnusoni

@dbt_metron I think there's a lot missing in here. If you want to create asset or IOC entities within the platform, you need to make sure you're ingesting that log type. You also need to make sure the parser is creating an asset/ioc entity during the normalization process. If you're not sure, you can look at the parser for that specific log type. A good example is the TANIUM_ASSET log type. It should be creating an asset entity when that log type is being ingested. On the other hand, we have a log type for TEQTIVITY_ASSETS but no parser. In that instance, you would have to create a custom parser for that log type that would create an asset entity.

Once you have the log type and parser to create the asset entity, it should show up in the platform. This same logic applies for IOC's. We have a log type and parser for ANOMALI_IOC, so IOCs should be created if you were to ingest that log. Whereas we have a log type of CYBERES_IOC but no parser, so you would have to create a custom parser that would take those logs and create an IOC.

The last option would be to convert the log into UDM yourself and then ingest the IOC or ASSET. Sometimes this is the easier route when the log is small and it's not worth creating a full parser.  You can convert the log to UDM following the UDM Schema (using python or something else), and ingest the log as UDM log type through a feed or the Ingestion API.

The following docs will come in handy if you need to write your own parser, or if you decide to convert it to UDM yourself.

• https://cloud.google.com/chronicle/docs/reference/udm-field-list#Asset
• https://cloud.google.com/chronicle/docs/reference/important-udm-fields
• https://cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers
• https://cloud.google.com/chronicle/docs/reference/parser-syntax
• https://cloud.google.com/chronicle/docs/reference/ingestion-api#createentities
• https://medium.com/@thatsiemguy/ioc-matching-in-chronicle-siem-45a97c0b91a8