You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This is a working document.

Notes

At a high level there are 4 broad categories in regards to Security Event Management (Or is this a Security Event Lifecycle?)

**There probably a body of work we can reference that spells this out.  ACTION: Literature review for that

Terms

This is place where we can standardize our language.

  • Security Data: This is raw data that by itself may not be enough to indicate a security event.
  • Security Event: 
  • Analytic

QUESTIONS

  1. In terms of security logging, should we handle ONAP components differently than Service Components hosted in ONAP?
  2. How do we handle the use case where ONAP is being used to deploy and manage a security infrastructure?
  3. What about security events in regards to the closed loop model?  Adversarial AI will be an issue that will need security monitoring in the near future.  Does this mean that orchestration / life cycle data from the DCAE needs to ingested by a SIEM?

References

  1. https://www.enisa.europa.eu/publications/security-in-5g-specifications
  2. https://www.enisa.europa.eu/publications/enisa-threat-landscape-report-for-5g-networks



  • No labels