...
Column | Description |
|---|---|
| ID of this row |
| ID of the credential |
| Timestamp of count reset event |
Monitor
The Monitor would likely need to be developed (presumably as an Open Source project).
The final component is the Monitor, responsible for determining when thresholds are reached and taking appropriate action, as well as for managing reset events. The most portable approach may be for the Monitor to periodically poll the database for counts, and then fire off events as appropriate. (It may be possible to leverage database trigger mechanisms to push events to the Monitor, but this is unlikely to be achievable in a cross-platform way.)
The Monitor would likely provide
- A polling mechanism to retrieve current counts
- Support for different thresholds to trigger different actions
- Notifications
- Credential expiration
- IAQ revocation (potentially without a credential being expired)
- API services
- Pull current state for a subject (useful, say, for integration with SSO or self-service tools)
- Reset counter (eg: on password change)
- User Interface
- Administer/configure Monitor
- Reporting on current counts and events
The Monitor would likely need to be developed (presumably as an Open Source project).See Also: Monitor Requirements