HEART security.login-failures H-11001
Many failed logins. Many failed login attempts.
| Code | HEART security.login-failures; inside a message "code": "security.login-failures" |
|---|---|
| H-number | H-11001: area 11, code 001 |
| Area | security: Logins, certificates, tampering |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every connected product |
Likely causes
- Someone is guessing passwords.
- A device, script or app still uses an old password.
- A person forgot their password and keeps trying.
- A default password left in place and found by a scanner.
How to fix or prevent it
- Read where the attempts come from: an address, a device, a user name.
- Update the old password in the device, script or app that keeps failing.
- Change any default password.
- Use strong passwords, and a second sign-in factor where the product offers it.
What the HEART does by itself
It raises a warning, and slows down or blocks the source for a time. It resolves when the attempts stop.
When to call service
If the attempts come from outside your network and do not stop.
Related codes
security.unexpected-accessH-11002: Unexpected accesssecurity.anomalyH-11007: Security anomaly
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)