HEART security.policy-violation H-11006
Policy violation. Something broke the owner's rules, such as data that should not have left.
| Code | HEART security.policy-violation; inside a message "code": "security.policy-violation" |
|---|---|
| H-number | H-11006: area 11, code 006 |
| Area | security: Logins, certificates, tampering |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Every connected product |
Likely causes
- Data tried to leave that the owner's rules keep private.
- An action was asked for that the owner's rules do not allow.
- A setting was changed in a way that breaks a rule.
- A rule that is wrong, and blocks normal use.
How to fix or prevent it
- Read the alert: it names the rule and what broke it.
- Fix whatever tried to break it.
- If the rule is wrong, change the rule, not the check.
What the HEART does by itself
It blocks what broke the rule where it can, such as data held back by the Valve, and raises an error alert.
When to call service
If personal or protected data may have left.
Related codes
security.anomalyH-11007: Security anomalysecurity.unexpected-accessH-11002: Unexpected accessdata.integrity-failedH-10005: Data integrity check failed
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)