Skip to main content

​
What’s included in C1 system logs?

System logs include a record of actions taken by the C1 API. The C1 API is used for all app-level actions and captures both end-user and administrative activities. C1 system logs are stored in OCSF (Open Cybersecurity Schema Framework), a leading open-source data format developed by AWS, IBM, and Splunk. Learn more about OCSF by viewing the OCSF schema documentation.

​
How do I get access to the system logs?

System logs are stored internally in C1 and can be accessed via API or exported to an external data source such as an S3 bucket or Azure Blob container.

​
Where can I see a list of all the API events included in the system logs?

You can download our authoritative list of API events, which is presented in Sigma Detection Format.
  • YAML format: Go to <YOUR C1 TENANT URL>/api/v1/ocsf-events.yaml
  • JSON format: Go to <YOUR C1 TENANT URL>/api/v1/ocsf-events.json

​
Sync C1 system logs into your SIEM

Follow this process to import C1 logs into your security information and event management (SIEM) platform.
This task requires the Super Administrator role in C1.

​
Step 1: Create an external data source

If you haven’t already done so, create an external data source to sync the system logs to.
Reusing an existing external data source?If you’re reusing an existing data source that you’ve already created and integrated with C1, ensure that it was created with the ability to accept writes. For example, for S3 buckets, the policy will require the "s3:PutObject" permission.

​
Step 2: Create a system log exporter

1
Navigate to Settings > System log and click Add exporter.
2
Set up the new exporter:
  • Give the exporter a name, such as “System log to S3”.
  • Select the Datasource you created in Step 1.
  • Optional. Input an file prefix.
  • Select your output format and compression algorithm.
3
Click Save.
Your system log exporter will now run every four to five minutes. You’ll see a Waiting status indicator between runs, and an Error status indicator if anything’s amiss. A new log file is generated for each run, each containing up to 2.5mb of uncompressed data. In a full day of activity, you should expect roughly 280 files to be exported to your external data source.

​
Step 3: Connect your SIEM

This step will vary depending on the SIEM that you are using. In general terms, however, you will want to add the datasource to your SIEM. A partial list of SIEM directions:

​
Using C1 logs with CrowdStrike Falcon Next-Gen SIEM

Ingesting an S3 bucket via the Amazon S3 Data Connector requires a Falcon Next-Gen SIEM subscription. Without it, the connector appears in the CrowdStrike Store but can’t be configured.
Because C1 system logs are OCSF, they map cleanly to CrowdStrike’s data model. When you set up the Amazon S3 Data Connector to ingest your external data source, select an OCSF parser so events normalize to the CrowdStrike Parsing Standard (CPS) rather than authoring your own. CrowdStrike’s Amazon Security Lake Data Connector includes an OCSF-to-CPS parser you can reference, and Next-Gen SIEM can also generate a parser for you. The connector listing covers the AWS resources you’ll create (an SQS queue for object-created notifications and an IAM role CrowdStrike assumes) and the current console steps. Once ingested, C1 access events are searchable and alertable alongside the rest of your Falcon telemetry.

​
Reading system log files

C1 system logs use the Open Cybersecurity Schema Framework (OCSF) to format log events. Check out the OCSF documentation for full details of OCSF API activity formatting, but here are a few key details to help you quickly make sense of C1 system log output.
  • “activity_id”: The “activity_id” entry in a log line tells you what type of API call activity triggered the event. By filtering logs by these activity IDs, you can zero in on key types of activity in the C1 system.
    • “activity_id”:1 - “Create” activity
    • “activity_id”:2 - “Read” activity
    • “activity_id”:3 - “Update” activity
    • “activity_id”:4 - “Delete” activity

​
Actor type classification

Breaking change, effective [RELEASE DATE]: two actor.user.type_id values below are changing for events generated from that date forward. If your queries or automation filter on these values, update them before this date. Events logged before [RELEASE DATE] aren’t affected.
The actor.user.type_id field identifies what kind of actor triggered an event. If you have queries that filter type_id = 1 to capture all human activity, update them to type_id IN (1, 2). If you have automation that filters type_id = 99 for machine identities, switch it to type_id = 4, or filter on the unaffected type string field instead. Each actor’s platform roles are listed by display name in actor.user.groups[], with a stable uid for each role.

​
API operation audience

API Activity events (class_uid 6003) include an unmapped.audience field describing who’s allowed to call that operation: basic_user, admin_only, super_admin_only, machine_only, or unassigned. The same value is available as audience= in api.request.flags.

​
Identity & Access events

C1 emits four Identity & Access event classes in addition to existing event types: If your pipeline routes events by class_uid and has a fallthrough or default handler, make sure these four classes are handled explicitly instead of falling into that default. Privilege-changing operations emit a paired API Activity event and Identity & Access event that share the same metadata.correlation_uid, so you can join them. This means privilege-changing operations now produce two events instead of one — if you have dashboards or metrics based on event volume, scope them to avoid double-counting.