io7m | single-page | multi-page | epub | Cardant User Manual 1.0.0-beta0002
9.1. Overview
Previous
9. Security
Up
10. Appendix: Schema: Type Package 1.0
Next

# 9.2. Security

- 9.2.1. Overview
- 9.2.2. Security Policy Violations

## 9.2.1. Overview

1
All command execution in the cardant server passes through a single code path that captures OpenTelemetry traces and publishes events. Administrators should write alerting rules in their metrics system of choice to watch for instances of the traces, metrics, and events described here; they almost certainly indicate malicious behaviour.
2
At the time of writing, events are published as part of a containing trace, and therefore the server must be configured to publish traces in order for an external monitoring system to be able to observe the events. The reason for this is that the OpenTelemetry Events API specification is not yet stable and so traces are currently the only way to publish events. It is expected that a stable version of the Events API will be released soon, and then the cardant server will switch to using that API directly (and this will require only log telemetry to be configured as opposed to full trace collection).

## 9.2.2. Security Policy Violations

1
If an operation attempts to violate the server's built-in security policy, an exception will be raised with an cardant.errorCode attribute set to error-security-policy-denied.
9.1. Overview
Previous
9. Security
Up
10. Appendix: Schema: Type Package 1.0
Next
io7m | single-page | multi-page | epub | Cardant User Manual 1.0.0-beta0002