Frame Sentinel as IDS IPS and EDR
This commit is contained in:
parent
1a5b6f1d8d
commit
6a09fbb7f9
10 changed files with 47 additions and 33 deletions
|
|
@ -80,12 +80,16 @@ Sentinel assumes:
|
|||
- The dashboard is read-only by design; it can display dry-run response plans
|
||||
but does not execute containment commands.
|
||||
- The current product does not perform automatic containment.
|
||||
- Sentinel's IPS scope is explicit prevention workflow: posture hardening,
|
||||
containment planning, and future reviewed `--apply` actions. It is not an
|
||||
inline network appliance and does not silently rewrite host state.
|
||||
|
||||
## Security Controls Already Present
|
||||
|
||||
| Control | Purpose |
|
||||
|---|---|
|
||||
| Hardened systemd unit | Limits daemon write surface and runtime privilege where possible. |
|
||||
| Explicit IPS workflow | Turns detections into reviewed prevention/containment plans without automatic remediation. |
|
||||
| Cooldown deduplication | Prevents alert storms from one persistent condition. |
|
||||
| Snapshot retention | Preserves evidence while bounding local disk growth. |
|
||||
| FIM self-watch | Detects changes to Sentinel's own files and service definitions. |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue