Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Find your local number: https://zoom.us/u/aee0gyHkh8

   Due to an urgent conflict today's meeting, 7/13/2020, has been cancelled.  The following email was sent out with a request for input regarding Maturity level security review requirements.

The main agenda item for today was to discuss incubation and maturity security requirements for blueprints.  Please review the updates that I have made to the following link concerning Incubation and Maturity:  PASS/FAIL Criteria for Vuls, Lynis and Kube-Hunter:

https://wiki.akraino.org/display/AK/Steps+To+Implement+Security+Scan+Requirements

Currently the difference between Incubation and Maturity Security Requirements is that exceptions are more readily granted for incubation.  Exceptions for maturity should be granted only for cases where the issue does not apply to the blueprint (ie specific code/configuration is not being used) or a separate security measure is being taken to mitigate the issue.  Any exception granted for the Maturity phase should be very clearly documented.

For Maturity we must require a higher security level than Incubation, yet these requirements need to be testable by BluVal and easily quantified.  If there are additional security measures that you feel should be added to the Maturity requirements for Akraino please respond to the security team, security@lists.akraino.org, with those recommendations for discussion.  Please do this as soon as possible because we need to provide all of our Maturity requirements to the TSC in the next two weeks for their review/approval.


 

Agenda:

ICN BP Security review (Bluval results): Kuralamudhan Ramakrishnan & Igor Duarte Cardoso: - 20 - 30 mins

...