Skip to content

Conversation

@irakledibm
Copy link
Contributor

@irakledibm irakledibm commented May 20, 2025

Summary

As artificial intelligence (AI) systems become increasingly integral to enterprise infrastructure, security teams require standardized, interoperable telemetry for detecting threats, ensuring compliance, and analyzing the behavior of complex AI workflows. This proposal introduces a structured extension of OCSF to support AI system observability and security telemetry through the addition of a new category, event classes, reusable objects, and specialized profiles.

Proposed Additions to OCSF

Category:

Category Name UID Description
AI System Activity 9 AI-specific events including inference operations, agent workflows, prompt security, and model telemetry.

Profiles:

Profile Name Purpose
AI Inference Adds latency, model info, token usage, and endpoints to inference events
AI Tool Describes capabilities, constraints, compliance, and risk of tools

Events:

Class Name Description
AI System Activity General telemetry about AI system operations
Model Inference Activity Captures LLM/ML inference events with token usage and confidence data
MCP Message Activity Standardizes Model Context Protocol (MCP) communication logs
Agentic RAG Workflow Execution Captures advanced RAG pipelines with stepwise traceability

Objects:

Object Name Description
Workflow Step Represents a single reasoning or tool step in an agentic workflow
Tool Call Details arguments, results, and errors from tools invoked in MCP format
Tool Object to represent metadata for AI tools used in agentic, communication or orchestration workflows.
Message Payload Represents MCP message payload

ocsf_categories

@irakledibm irakledibm marked this pull request as ready for review May 26, 2025 18:03
@irakledibm irakledibm changed the title DRAFT - Addition of AI Systems Activity Category, Classes, Profiles and Objects Addition of AI Systems Activity Category, Classes, Profiles and Objects May 26, 2025
lukas-krecan-s1 and others added 4 commits May 26, 2025 15:19
We need to convey the information that a [Service
Account](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-service-accounts)
was used. As there already is a `System` account type in the `user`, it
seems fitting to add the Service account to the same enum.

Signed-off-by: Lukáš Křečan <[email protected]>
@irakledibm irakledibm force-pushed the main branch 2 times, most recently from b730789 to efa0824 Compare May 26, 2025 20:14
floydtree and others added 6 commits May 26, 2025 16:16
The newly added linter action, was causing workflow failures for
spelling errors, (which weren't really incorrect spellings, but more so,
generally accepted terms that were simply not in the dictionary.) That
is besides the point though, there was common desire in the community to
not error out, but throw warnings. Which makes sense, considering the
fairly common usage of "non-standard" English words in our industry.

This PR updates the workflow to warn, instead of erroring out on
spelling errors. All the warning should be visible inline. The PR
creator and reviewers can then make discretionary call about the
applicability of warnings.

For example, the inline warnings look like the following -

![image](https://github.com/user-attachments/assets/95a679e0-ca96-4a45-920d-31eb63eb7407)

Additionally, I am cleaning up & optimizing this workflow along with
removing unused workflows from the repo.

---------

Signed-off-by: Rajas Panat <[email protected]>
This reverts commit 810229d.
We have a few cases when we need to delete findings. For example:

1. The finding was created by misconfigured or buggy producer. When the
issues is discovered, the producer needs to inform all services
consuming the data that the finding is not valid anymore and should be
discarded.
2. A customer was evaluating the product, created some test findings and
now wants to start using the product in production. We need to delete
the data from POC.

Signed-off-by: Lukáš Křečan <[email protected]>
@floydtree floydtree marked this pull request as draft June 3, 2025 16:43
@mikeradka mikeradka removed the v1.7.0 label Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants