Log in
Skip to sidebar
Skip to main content
Linked Applications
Loading…
Confluence
Spaces
Questions
Terms
Hit enter to search
Help
Online Help
Keyboard Shortcuts
Feed Builder
What’s new
Available Gadgets
About Confluence
Log in
Developer Wiki
Pages
Blog
Terms
Questions
Space shortcuts
Shared links
File lists
Meeting notes
JIRA Reports
How-to articles
Retrospectives
Product requirements
Page tree
Browse pages
Configure
Space tools
View Page
A
t
tachments (0)
Page History
Page Information
View in Hierarchy
View Source
Export to PDF
Export to Word
Export to Markdown
Copy Page Tree
Pages
…
Technical Steering Committee (TSC)
TSC Subcommittees
ONAP Security coordination
ONAP Next Generation Security & Logging Architecture
ONAP Security Event Management
Log Alerting
Page History
Versions Compared
Old Version
1
changes.mady.by.user
Robert Heinemann
Saved on
Sep 24, 2021
compared with
New Version
Current
changes.mady.by.user
Robert Heinemann
Saved on
Sep 24, 2021
View Page History
Key
This line was added.
This line was removed.
Formatting was changed.
Possibly to include mitigation and actions.
If we expect ONAP to respond to security events in a closed loop manner, then there needs to be a way for events generated by the SIEM to be ingested back into ONAP.
Overview
Content Tools
{"serverDuration": 117, "requestCorrelationId": "42ae21521a7a90e7"}