HEART security.unexpected-access H-11002
Unexpected access. Access from an unknown place, or at an unusual time.
| Code | HEART security.unexpected-access; inside a message "code": "security.unexpected-access" |
|---|---|
| H-number | H-11002: area 11, code 002 |
| Area | security: Logins, certificates, tampering |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every connected product |
Likely causes
- A sign-in from a new place, network or device.
- Access at a time nobody normally uses it.
- Stolen or leaked credentials.
- A shared account used by someone new.
How to fix or prevent it
- Check whether it was you or someone you allowed.
- If not: change passwords, and revoke sessions and API keys.
- Check what was done during that access.
- Stop sharing accounts: give each person their own.
What the HEART does by itself
It raises a warning with when and from where. It does not lock out the owner by itself.
When to call service
If it was not you or anyone you allowed.
Related codes
security.login-failuresH-11001: Many failed loginssecurity.anomalyH-11007: Security anomalysecurity.policy-violationH-11006: Policy violation
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)