Describe Sentinel as endpoint detection and response
This commit is contained in:
parent
a51478fa22
commit
812cf0c836
6 changed files with 28 additions and 25 deletions
|
|
@ -1,8 +1,9 @@
|
|||
# Enodia Sentinel Roadmap
|
||||
|
||||
This roadmap moves Enodia Sentinel from a host IDS into a host security platform:
|
||||
detect, verify, investigate, respond, and assure. Dates are intentionally not
|
||||
promised here; the sequence matters more than calendar precision.
|
||||
This roadmap moves Enodia Sentinel from single-host endpoint detection and
|
||||
response into a fuller host security platform: detect, verify, investigate,
|
||||
respond, and assure. Dates are intentionally not promised here; the sequence
|
||||
matters more than calendar precision.
|
||||
|
||||
## Release Tracks
|
||||
|
||||
|
|
@ -145,7 +146,7 @@ Exit criteria:
|
|||
- Multi-stage correlation raises one higher-confidence incident without hiding
|
||||
the underlying raw alerts.
|
||||
|
||||
## v1.1.1: IDS Quality and Rule Operations
|
||||
## v1.1.1: Detection Quality and Rule Operations
|
||||
|
||||
Purpose: make detection coverage easier to audit, tune, and extend without
|
||||
turning Sentinel into a noisy rules dump.
|
||||
|
|
@ -170,7 +171,7 @@ Exit criteria:
|
|||
|
||||
- Operators can inspect, test, document, and tune detection rules without
|
||||
reading Python source.
|
||||
- Every shipped IDS rule has reproducible fixture/drill coverage and stable
|
||||
- Every shipped detection rule has reproducible fixture/drill coverage and stable
|
||||
operator documentation.
|
||||
|
||||
## v1.2: Fleet Mode
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue