LLM: Standardized fields for LLM Security and protection [LLM detection rules category]

[susan-shu-c]

Area(s)

area:gen-ai, llm

Is your change request related to a problem? Please describe.

Continuation of https://github.com/open-telemetry/semantic-conventions/issues/1007

To prevent threats to LLM systems, such as misuse, and to log content filters, proposing standardized fields for the purpose of secure and safe LLM usage. Based on frameworks such as OWASP’s LLM Top 10 and MITRE ATLAS.

An example is that a user may be using various LLM vendors or their own deployments, and wish to log all of them in a standardized manner. Our team has published a blog proposing standardized fields for LLM Security, led by @Mikaayenson.

From previous discussion in https://github.com/open-telemetry/semantic-conventions/issues/1007, to make this proposal easier to move forward, here's a prioritized, much narrowed-down subset of proposed fields.

The code of our shipped detection rules can be viewed here:

• LLM Threat Hunting Queries
• LLM detection rules (Bedrock)

Describe the solution you'd like

Proposing the following fields that are used in our shipped detection rules. The rules detect and prevent DoS, inappropriate usage, LLMJacking.

Category	Field	Type	Description	Rules (details linked in above section)	Comments
Policy Enforcement Fields	gen_ai.policy.name	keyword	Name of the specific policy that was triggered.	* aws_bedrock_guardrails_multiple_violations_in_single_request
	gen_ai.policy.action	keyword	Action taken due to a policy violation, such as blocking, alerting, or modifying the content.	* aws_bedrock_guardrails_multiple_violations_in_single_request * aws_bedrock_high_confidence_misconduct_blocks_detected
	gen_ai.policy.confidence	float	Confidence level in the policy match that triggered the action, quantifying how closely the identified content matched the policy criteria.	* aws_bedrock_high_confidence_misconduct_blocks_detected
Compliance Fields	gen_ai.compliance.violation_detected	boolean	Indicates if any compliance violation was detected during the interaction.	* aws_bedrock_guardrails_multiple_violations_by_single_user
	gen_ai.compliance.violation_code	keyword	Code identifying the specific compliance rule that was violated.	* aws_bedrock_high_confidence_misconduct_blocks_detected
Performance Metric Fields	gen_ai.performance.request_size	long	Size of the request payload in bytes.	* llm_dos_resource_exhaustion_detection

Describe alternatives you've considered

Alternatives are to submit these fields only to ECS, but since the donation of ECS, the standard is to discuss and propose to OTel.

Additional context

No response