ONAP Security Review Questionnaire Template
"The project MUST have performed a security review within the last 5 years. This review MUST consider the security requirements and security boundary." – Best Practices Badging Criterion
Please fill in the survey questions for each of the following sections. In all cases, answer the questions from the point of view for YOUR application within ONAP.
For each one, additional information on the question is available to be read by clicking the arrow following the question.
Most items in this questionnaire are related to specific Best Practices Badging Criteria. The name of the associated criterion is listed at the end of the toggled "additional information" section, along with an indication of the badging level of the question, P=passing, S=silver and G=gold.
Once the security review is completed, the application owner can update the gold level badging question "security-review" as having been accomplished.
Security Knowledge
Know Secure Design
Do the committers and PTL know how to design secure software? Do the reviewers of OJSI tickets know secure design?
Your Answers-Please Explain | SECCOM Feedback / Recommendations |
|---|---|
|
|
Implement Secure Design
Do the committers and PTL apply secure design principles when reviewing software for merging?
Your Answer-Please Explain | SECCOM Feedback / Recommendations |
|---|---|
|
|
Know Common Errors
Do the committers and PTL understand commonly found errors (and how to counter or mitigate them)? Do they apply these principles when reviewing software for merging?
Your Answers-Please Explain | SECCOM Feedback / Recommendations |
|---|---|
|
|
No Leaked Credentials
Do the committers and PTL verify that there are no non-test credentials and no non-test private keys in code to be merged?
Your Answer-Please Explain | SECCOM Feedback / Recommendations |
|---|---|
|
|
Security Documentation
Documentation Architecture
Does your project have an architecture or high level design documented?
If so, please provide a URL to the pages on wiki.onap.org or onap.readthedocs.io that have the architecture or high level design. If not, please describe the high level design here using one or more paragraphs.
Your Answer-Please Describe | SECCOM Feedback / Recommendations |
|---|---|
|
|
Documentation Security
Does your project have a description of what a user of your project can and cannot expect in terms of security from the software produced by the project, (In other words, what are its 'security requirements'?)
If so, please provide a URL to the page(s) on wiki.onap.org or onap.readthedocs.io. If not, please describe the security requirements here using one or more paragraphs.
Your Answer-Please Describe | SECCOM Feedback / Recommendations |
|---|---|
|
|
Assurance Case
Does your project actually meet its documented security requirements?
If so, please provide a URL to the page(s) on wiki.onap.org or onap.readthedocs.io that describe how the project meets its security goals. If not, please describe here (using one or more paragraphs) how the project meets its security goals.
Your Answer-Please Describe | SECCOM Feedback / Recommendations |
|---|---|
|
|