Scenario: Monitoring & alerting
Defined in model.py:574
OSSEC watches the app server; encrypted alerts are mailed to admins.
4 open threats, highest risk 6 medium · 4 threats in all · 4 data flows · 3 affected components
Data Flow Diagram
Sequence Diagram
Show data flows
| ID | Name | Source | Sink | Type |
|---|---|---|---|---|
| 1 | Ship events | OSSEC client | OSSEC server | Request |
| 2 | Raise alert | OSSEC server | Postfix | Request |
| 3 | Relay mail | Postfix | SMTP relay | Request |
| 4 | Deliver to admin | SMTP relay | Administrator | Request |
Applicable threats
| Threat | Component | Status | Risk | After mitigations | Mitigations |
|---|---|---|---|---|---|
| OSSEC rules configuration error on application server THREAT167 | OSSEC client | partially mitigated | 9 high | 6 medium | Use of Ansible for configuration management for servers |
| OSSEC and/or Journalist alert SMTP account credentials compromised THREAT69 | Postfix | partially mitigated | 2 low | 2 low | OSSEC emails are gpg encrypted; OSSEC emails should be signed |
| OSSEC and/or Journalist alert private key compromised THREAT70 | Postfix | partially mitigated | 2 low | 2 low | OSSEC logs do not contain sensitive information. |
| SMTP relay compromised THREAT71 | SMTP relay | partially mitigated | 2 low | 2 low | OSSEC emails are gpg encrypted; OSSEC emails should be signed |