OpenDaylight Vulnerability Managment

opendaylight vulnerability process

#OpenDaylight - Vulnerability Management

[TOC]

##Motivation

The OpenDaylight project has gained enough momentum and popularity that the responsible management of security issues in the upstream community is warranted. OpenDaylight has in fact had its first [CVE](http://seclists.org/bugtraq/2014/Aug/75) assigned via an independent security researcher, who at the time had no process to follow. This **must** change.


----------


## Proposed Security Response Procedure

### Reference procedures
In an attempt to avoid re-inventing the wheel, the OpenDaylight vulnerability management process borrows unashamedly from the following procedures:

 - [The Linux Kernel process for reporting security issues](https://www.kernel.org/doc/Documentation/SecurityBugs)
 - [The OpenStack vulnerability management process](https://wiki.openstack.org/wiki/Vulnerability_Management)
 - [Recommendations for a minimal security response process](https://securityblog.redhat.com/2013/01/30/a-minimal-security-response-process/)
 
### Security supported projects
As OpenDaylight is a hive of innovation and change it is necessary to outline the criteria for a project under the OpenDaylight umbrella to be security supported, and to be subject to the vulnerability management process. 

The [OpenDaylight project lifecycle & release process](http://www.opendaylight.org/project-lifecycle-releases) references six succinct stages that may categorise a project. These categories have been used to outline the recommended security support status for projects below.

Project Type	| Support Status
--------------  | ------------
Proposal	    | Not security supported.
Incubation	    | Not security supported.
Mature	        | Subject to audit prior to receiving security supported status.
Core	        | Security supported. 
Top Level	    | Security supported. Requires member on security team.
Archived	    | Not security supported.

Before an OpenDaylight project is considered  security supported it needs to undergo a security audit and have any issues addressed. Once receiving security supported status, all security issue will need to be addressed under embargo and have a security advisory issued. 

Top level projects should try to provide at least one developer to work on the security team. Having connections within the development organization along with understanding of the implementation details is very useful when triaging security issues.  


 
### Security supported versions

A commitment needs to be made for all security supported projects within OpenDaylight to backport security fixes to the previous releases of the products affected by the flaw. Backporting should be done in alignment with release engineering current maintenance strategy.

> **Note**: 
> The security team needs to provide accurate information about the version the flaw was first introduced so that vendors operating still maintaining older product lines can backport fixes outside of the upstream maintenance window.
   



### Vulnerability Management Workflow

#### Workflow for private security issues

```flow
private_report=>start: Receive private bug report
via [email protected] list
create_security_tracker=>operation: Create private security bug
grant_access_to_bug_reporter=>operation: Add reporter to bug
grant_access_to_core_dev=>operation: Add security contact from project to bug
is_security_flaw=>condition: Confirmed as 
security vulnerability
add_statement=>operation: Add statement from security team 
indicating why bug is not 
considered a security flaw
open_bug_normal_fix=>end: Open bug and 
fix as normal
develop_patch_privately=>operation: Develop patch
develop_impact_description=>operation: Develop impact description
wait_for_patch=>operation: Wait for fix
patch_ready=>condition: Patch ready 
and peer reviewed?
request_cve=>operation: Request CVE and add it to bug
set_disclosure_date=>operation: Coordinate disclosure date
advanced_notification=>operation: Send advanced notification 
of disclosure date to stakeholders 
wait_for_disclosure_date=>operation: Wait for disclosure date
disclosure_date_reached=>condition: Disclosure
 date reached?
open_bug_disclosure_date=>operation: Open bug to public
commit_fix=>operation: Commit fix
publish_advisory=>operation: Publish advisory to 
[email protected], 
[email protected]
follow_normal_release_process=>end: Follow normal release process

private_report->create_security_tracker->grant_access_to_core_dev->grant_access_to_bug_reporter->is_security_flaw
is_security_flaw(no)->add_statement->open_bug_normal_fix
is_security_flaw(yes)->develop_impact_description->develop_patch_privately->wait_for_patch->patch_ready
patch_ready(no)->wait_for_patch
patch_ready(yes)->request_cve->set_disclosure_date->advanced_notification->wait_for_disclosure_date->disclosure_date_reached
disclosure_date_reached(no)->wait_for_disclosure_date
disclosure_date_reached(yes)->open_bug_disclosure_date->commit_fix->publish_advisory->follow_normal_release_process
```

#### Reception
A public page must be made available detailing the OpenDaylight vulnerability management process, and providing a single point of contact for contacting the security team. Preferably this should be a private email list that only members of the OpenDaylight security team have access to.
> **Note**: This list doesn't exist yet... (I don't think?) If not we should aim for <[email protected]>

**Extent of disclosure** :
 
 - Original Reporter
 - OpenDaylight Security Team

**Next Steps**:
 
 1. Send *reception confirmation email*
 2. Create private security bug
 3. Add reporter to private security bug
 4. Add project security contact to help triage the flaw

#### Triage
The bug must then be confirmed to be a security problem. This may require the inclusion of a subject matter expert to determine if the problem needs to be treated as a security flaw. If the bug is determined not be a security issue then a statement should be added indicating why, the bug should then be opened and fixed by following the standard OpenDaylight development process. 

Should all parties agree that the issue is a security flaw then all parties need to work on determining the affected product, assessing the risk to OpenDaylight users, and proposing a fix to the flaw. All of this work **must** be done under embargo. Proposed fixes must not be committed to SCM, and the problem should not be discussed outside of those that have been added to the bug. 

**Extent of Disclosure:**

 - Original Reporter
 - OpenDaylight Security Team
 - Subject matter expert (optional)

**Next Steps (status: confirmed)**:

 1. Post the *confirmed security issue* notification in the bug
 2. Determine which versions of the product are affected by the flaw
 3. Draft an impact description
 4. Confirm that the original reporter wants to be credited for finding the flaw
 5. Propose a fix / patch for the flaw
 6. Get the patch peer reviewed
 
**Next Steps (status: non-security)**:

 1. Post a statement for non-security issues in the bug
 2. Change the bugs security status from private to public
 3. Follow the normal OpenDaylight development process to get the issue fixed if necessary

#### Pre-disclosure 

When a patch has been developed and peer reviewed it is then possible to start planning on how and when to announce the issue. This involves agreeing on a disclosure date and notifying any downstream stakeholders.

> TODO

#### Disclosure date
When the coordinated disclosure date has been reached the assigned member from the OpenDaylight security team must perform the following tasks. 

> TODO 

#### Post-disclosure

Post disclosure the standard development process applies. Some additional book-keeping tasks can be undertaken in this phase

> TODO

### Handling public security issues

> TODO What happens if an issue is leaked? 

### Communication 
#### Message format
All messages communicated formally by the OpenDaylight security team should be in a well formed YAML format. This includes statements in bugs, as well as published advisories. This approach will provide a foothold for future reporting, automation and conversion to more standardised formats such as [CVRF](http://www.icasi.org/cvrf-1.1).

#### Reception confirmation email

Upon reception of a security report the OpenDaylight security team needs to clearly indicate the expectation of how the issue will be handled. 

> Thank-you for your security report. 

>The OpenDaylight security team has created a private security bug to track this issue. Please provide us with your OpenDaylight bugzilla ID so we can add you to the tracker. All communications and decisions about how this issue will be handled will be recorded on the this bug to provide proper tracking.

> ```{{ bugzilla_tracker_url }}```

> Regards, 

> --
> ```{{ opendaylight_security_team_member }}``` 
> OpenDaylight Security Team


#### Confirmed security issues

Clear instructions need to be provided to all parties involved with the fix as to how the issue needs to be fixed. When the flaw is confirmed, the following statement should be added to the bug by a member of the security team. 

> \#security-status: confirmed
> 
> This issue has been confirmed as a security vulnerability in ```{{ product }}``` and is to be fixed under the OpenDaylight embargoed security vulnerability process.  Please do not discuss or disclose details about this flaw prior to the agreed disclosure date (TBA). All decisions, discussions, and proposed patches and reviews are to be done via this tracking bug only. 

> If are you unsure of this process please refer to``` {{ opendaylight_security_process_url}}``` for more detailed instructions.
  
#### Impact description

The impact description needs to provide an accurate description of the flaw, how it affects the product, and outline the version range that is affected. The impact description should be entered into the tracking bug and reviewed for correctness. 

> title: ```{{ impact description title }}```

> reporters: 
> &nbsp;&nbsp;&nbsp;&nbsp;- name: ```{{ reporter_name }}```
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  company: ```{{ reporter_company }}```

> affects:
&nbsp;&nbsp;&nbsp;&nbsp;- product:  ```{{ product }}```
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; version: ```{{ version_range }}```

> risk-assessment:
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impact-rating: ```{{ impact_rating}}```

> description: >
> &nbsp;&nbsp;&nbsp;&nbsp;```{{ reporter_name }}``` from ```{{ reporter_company }}``` 
> &nbsp;&nbsp;&nbsp;&nbsp;reported a vulnerability in ```{{ product }}``` ....
>

Version
:	The version string must explicitly indicate the range of products affected by the flaw. 
> **Todo**: Maybe this format https://github.com/victims/victims-cve-db#version-string-common?  

Risk Assessment
:	The security team should provide a judgement call for the severity of the issue for the most common use case of the project. Suggested impact rating categories:

      - **Critical**: This rating is given to flaws that could be easily exploited by a remote unauthenticated attacker and lead to system compromise (arbitrary code execution) without requiring user interaction. These are the types of vulnerabilities that can be exploited by worms. Flaws that require an authenticated remote user, a local user, or an unlikely configuration are not classed as Critical impact.
      
      - **Important**: This rating is given to flaws that can easily compromise the confidentiality, integrity, or availability of resources. These are the types of vulnerabilities that allow local users to gain privileges, allow unauthenticated remote users to view resources that should otherwise be protected by authentication, allow authenticated remote users to execute arbitrary code, or allow local or remote users to cause a denial of service.

      - **Moderate**: This rating is given to flaws that may be more difficult to exploit but could still lead to some compromise of the confidentiality, integrity, or availability of resources, under certain circumstances. These are the types of vulnerabilities that could have had a Critical impact or Important impact but are less easily exploited based on a technical evaluation of the flaw, or affect unlikely configurations.
	  
      - **Low**: This rating is given to all other issues that have a security impact. These are the types of vulnerabilities that are believed to require unlikely circumstances to be able to be exploited, or where a successful exploit would give minimal consequences.
> **Note**: Formal methods such as [CVSS](http://www.first.org/cvss) may follow. 

Description
: The description must endeavour to accurately depict the nature of the flaw. Information that should be included must indicate the attack vector that is exposed by the flaw and the initial access level required by the attacker. Where applicable advice on how an operator may audit for abuse of the flaw within their environment.

#### CVE Request

To ensure proper traceability a CVE identifier needs to be requested from a CNA. An email requesting a CVE should be sent to either <[email protected]> or <[email protected]>. The email must be GPG-signed and GPG-encrypted.

> A vulnerability was discovered in OpenDaylight (see below). In order
> to ensure full traceability, we need a CVE number assigned that we can
> attach to private and public notifications. Please treat the following
> information as confidential until further public disclosure.
> 
> ```{{ impact_description }}```
> 
> Thanks in advance,
> 
> --  
> ```{{ opendaylight_security_team_member }}```
> OpenDaylight security team

#### Advanced notification

In the spirit of [responsible disclosure](http://en.wikipedia.org/wiki/Responsible_disclosure), large operators or vendors selling a derivative of OpenDaylight software should be given advanced notification of security issues to patch their products prior to making the details of the flaw public. A timeline of 3-5 working days should be allowed for stakeholders to assess the impact on their products and services.

> This is an advance warning of a vulnerability discovered in OpenDaylight,
> to give you, as downstream stakeholders, a chance to coordinate the
> release of fixes and reduce the vulnerability window. Please treat the
> following information as confidential until the proposed public
> disclosure date.
> 
> ```{{ impact_description }}```
> 
> Proposed patch: See attached patches. Unless a flaw is discovered in
> them, these patches will be merged to ```{{ branches }}``` on the public
> disclosure date.
> 
> CVE: ```{{ cve_id }}```
> 
> Proposed public disclosure date/time: ```{{ disclosure_date }}```. Please do
> not make the issue public (or release public patches) before this
> coordinated embargo date.
> 
> Regards,
> 
> -- 
> ```{{ opendaylight_security_team_member }}```
>  OpenDaylight Security Team

#### Advisory

The advisory notification builds on the existing impact description however it includes all the relative details of the fix. Each advisory should be given a unique identifier. This will be of the format ```<year>-<seq>```. Where _seq_ is a number that is incremented for each advisory issued for a given year.

> opendaylight-advisory: ```{{ odsa_id }}```
> cve: ```{{cve_id }}```
> advisory-date: ```{{ date_announced }}```

> ```{{ impact_description }}```

> changes:
> \# ```{{ release_name }}```
  &nbsp;&nbsp;- branch: ```{{ branch }}```
&nbsp;&nbsp;&nbsp; commit: ```{{ commit_hash }}```
&nbsp;&nbsp;&nbsp;  review: https://git.opendaylight.org/gerrit/#/c/```{{review_id}}```
>

> release-notes: >
> &nbsp;&nbsp;&nbsp;&nbsp; This fix will be included in the ```{{ milestone }}``` development milestone 
> &nbsp;&nbsp;&nbsp;&nbsp; and in a future ```{{ next_stable }}``` release.

> bug-tracker:  https://bugs.opendaylight.org/show_bug.cgi?id=```{{ bugzilla_id }}```

> -- 
> ```{{ opendaylight_security_team_member }}```
> OpenDaylight Security Team

#### Statement for non-security issues

In the cases where a potential security flaw has been reported but the OpenDaylight security team have determined that it is not to be fixed under the embargoed security process a statement indicating why this decision has been made. 

> \#security-status: wontfix
> statement:>
> &nbsp;&nbsp;&nbsp;&nbsp;The OpenDaylight security team has analysed this report and determined 
> &nbsp;&nbsp;&nbsp;&nbsp; that it is not a security issue. ```{{ reason }}```
> 
>  &nbsp;&nbsp;&nbsp;&nbsp;This bugs privacy status will now be changed to public, and the bug should 
>  &nbsp;&nbsp;&nbsp;&nbsp;be fixed following the normal development process. We would like to thank 
>  &nbsp;&nbsp;&nbsp;&nbsp;```{{ reporter }}``` for bringing this issue to our attention.


#### Information to include in commit message

The commit message for a vulnerability fix should include the following tag on a line by itself:
> \#security-fix: ```{{ cve_id }}```


##Roadmap

### Action Items

Topic | Assignee | Description
-|-|-
infrastructure | unassigned | Create a private mailing list for security team
infrastructure | unassigned | Enable private bugs in bugzilla
infrastructure | unassigned | Create a public page indicating contact information for the security team. This information must include the public GPG keys for each member of the security team.
documentation | unassigned | Create a public page detailing the vulnerability management process and how to report security problems to OpenDaylight
documentation | unassigned | Create a public document indicating the security status of each OpenDaylight project.
documentation | unassigned | Document the expectations around the audit required for projects to receive 'security supported' status. This might include things like attack surface, dependency analysis, or just how to record the audit results. 
organizational | unassigned | Form the security team. Decide when an how often meetings will be held. 
organizational | unassigned | Establish a list of downstream stakeholders that should be eligible for advanced notification of security issues. Inform them of this security process and communicate the expectations. Elicit feedback.
communication | unassigned | Ensure the new security process is announce on all major mailing lists.
future_work | unassigned | Work on automating the process to reduce human error
future_work | unassigned | Automate the mining of advisory information to allow for analysis of security landscape for each security supported project
future_work | unassigned | Automatically export advisory data in the standardized CVRF  




> Written with [StackEdit](https://stackedit.io/).

opendaylight_security_process

#OpenDaylight - Vulnerability Management

[TOC]

## Glossary

Term 	| Definition 
--------- 	| ------------
Embargo |  A time period where vendors have access to details concerning the security vulnerability, with an understanding not to publish these details or the fixes they have prepared. The embargo ends with a coordinated release date (“CRD”). [[source]](https://securityblog.redhat.com/2013/01/30/a-minimal-security-response-process/)



----------

##Motivation

The OpenDaylight project has gained enough momentum and popularity that the responsible management of security issues in the upstream community is warranted. OpenDaylight has in fact had its first [CVE](http://seclists.org/bugtraq/2014/Aug/75) assigned via an independent security researcher, who at the time had no process to follow. This **must** change.


----------


## Proposed Security Response Procedure

### Reference procedures
In an attempt to avoid re-inventing the wheel, the OpenDaylight vulnerability management process borrows unashamedly from the following procedures:

 - [The Linux Kernel process for reporting security issues](https://www.kernel.org/doc/Documentation/SecurityBugs)
 - [The OpenStack vulnerability management process](https://wiki.openstack.org/wiki/Vulnerability_Management)
 - [Recommendations for a minimal security response process](https://securityblog.redhat.com/2013/01/30/a-minimal-security-response-process/)
 
### Security supported projects
As OpenDaylight is a hive of innovation and change it is necessary to outline the criteria for a project under the OpenDaylight umbrella to be security supported, and to be subject to the vulnerability management process. 

The [OpenDaylight project lifecycle & release process](http://www.opendaylight.org/project-lifecycle-releases) references six succinct stages that may categorise a project. These categories have been used to outline the recommended security support status for projects below.

Project Type	| Support Status
--------------  | ------------
Proposal	    | Not security supported.
Incubation	    | Not security supported.
Mature	        | Subject to audit prior to receiving security supported status.
Core	        | Security supported. 
Top Level	    | Security supported. Requires member on security team.
Archived	    | Not security supported.

Before an OpenDaylight project is considered  security supported it needs to undergo a security audit and have any issues addressed. Once receiving security supported status, all security issue will need to be addressed under [embargo](#glossary) and have a security advisory issued. 

Top level projects should try to provide at least one developer to work on the security team. Having connections within the development organization along with understanding of the implementation details is very useful when triaging security issues.  


 
### Security supported versions

A commitment needs to be made for all security supported projects within OpenDaylight to backport security fixes to previous releases of the products affected by the flaw. Backporting is only required for previous releases that are still maintained, according to the release engineering current maintenance strategy.

> **Note**: 
> The security team needs to provide accurate information about the version the flaw was first introduced so that vendors operating still maintaining older product lines can backport fixes outside of the upstream maintenance window.
   



### Vulnerability Management Workflow

#### Workflow for private security issues

```flow
private_report=>start: Receive private bug report
via [email protected] list
create_security_tracker=>operation: Create private security bug
grant_access_to_bug_reporter=>operation: Add reporter to bug
grant_access_to_core_dev=>operation: Add security contact from project to bug
is_security_flaw=>condition: Confirmed as 
security vulnerability
add_statement=>operation: Add statement from security team 
indicating why bug is not 
considered a security flaw
open_bug_normal_fix=>end: Open bug and 
fix as normal
develop_patch_privately=>operation: Develop patch
develop_impact_description=>operation: Develop impact description
wait_for_patch=>operation: Wait for fix
patch_ready=>condition: Patch ready 
and peer reviewed?
request_cve=>operation: Request CVE and add it to bug
set_disclosure_date=>operation: Coordinate disclosure date
advanced_notification=>operation: Send advanced notification 
of disclosure date to stakeholders 
wait_for_disclosure_date=>operation: Wait for disclosure date
disclosure_date_reached=>condition: Disclosure
 date reached?
open_bug_disclosure_date=>operation: Open bug to public
commit_fix=>operation: Commit fix
publish_advisory=>operation: Publish advisory to 
[email protected], 
[email protected]
follow_normal_release_process=>end: Follow normal release process

private_report->create_security_tracker->grant_access_to_core_dev->grant_access_to_bug_reporter->is_security_flaw
is_security_flaw(no)->add_statement->open_bug_normal_fix
is_security_flaw(yes)->develop_impact_description->develop_patch_privately->wait_for_patch->patch_ready
patch_ready(no)->wait_for_patch
patch_ready(yes)->request_cve->set_disclosure_date->advanced_notification->wait_for_disclosure_date->disclosure_date_reached
disclosure_date_reached(no)->wait_for_disclosure_date
disclosure_date_reached(yes)->open_bug_disclosure_date->commit_fix->publish_advisory->follow_normal_release_process
```

#### Reception
A public page must be made available detailing the OpenDaylight vulnerability management process, and providing a single point of contact for contacting the security team. Preferably this should be a private email list that only members of the OpenDaylight security team have access to. The public GPG keys associated with the email queue must also be published to allow reporters to GPG encrypt the email.

The OpenDaylight security team must also monitor development mailing lists and bug creation feeds to ensure that there are no issues that have been publicly reported which need to be treated as a security flaw. Should such a situation exist the *public security issue workflow* needs to be followed.

Upon receiving a privately reported security issue the OpenDaylight security team needs to complete the following tasks.

**Extent of disclosure** :
 
 - Original Reporter
 - OpenDaylight Security Team

**Next Steps**:
 
 1. Send *reception confirmation email*
 2. Create private security bug
 3. Add reporter to private security bug
 4. Add project security contact to help triage the flaw

#### Triage
The bug must then be confirmed to be a security problem. This may require the inclusion of a subject matter expert to determine if the problem needs to be treated as a security flaw. If the bug is determined not be a security issue then a statement should be added indicating why, the bug should then be opened and fixed by following the standard OpenDaylight development process. 

Should all parties agree that the issue is a security flaw then all parties need to work on determining the affected product, assessing the risk to OpenDaylight users, and proposing a fix to the flaw. All of this work **must** be done under [embargo](#glossary). Proposed fixes must not be committed to SCM, and the problem should not be discussed outside of those that have been added to the bug. 

**Extent of Disclosure:**

 - Original Reporter
 - OpenDaylight Security Team
 - Subject matter expert (optional)

**Next Steps (status: confirmed)**:

 1. Post the *confirmed security issue* notification in the bug
 2. Determine which versions of the product are affected by the flaw
 3. Draft an impact description
 4. Confirm that the original reporter wants to be credited for finding the flaw
 5. Propose a fix / patch for the flaw
 6. Get the patch peer reviewed
 
**Next Steps (status: non-security)**:

 1. Post a statement for non-security issues in the bug
 2. Change the bugs security status from private to public
 3. Follow the normal OpenDaylight development process to get the issue fixed if necessary

#### Pre-disclosure 

When a patch has been developed and peer reviewed it is then possible to start planning on how and when to announce the issue. This involves agreeing on a disclosure date and notifying any downstream stakeholders.

**Extent of Disclosure**:

 - Original Reporter
 - OpenDaylight Security Team
 - Subject Matter Expert (optional)
 - Downstream stakeholders

**Next Steps**:
 
 1. Send *CVE request email* to <[email protected]>
 2. Agree on disclosure date with original reporter. This will most likely need to fall on a Tuesday, Wednesday, or a Thursday. It should also be set sufficiently in the future to allow downstream stakeholders enough time to assess their risk. (3-5 business days). Also ensure a developer is available at that time to push up the fix. 
 3.  Send *advanced notification* email to list of downstream stakeholders.
 4. Re-test the patch. Ensure that it still applies to the various branches and that all unit tests pass.
 


#### Disclosure date
When the coordinated disclosure date has been reached the assigned member from the OpenDaylight security team must perform the following tasks. 

**Extent of Disclosure**: 

 - Everybody. The issue will now be public. 

**Next steps**:

1. Re-test the patch and make sure all unit tests pass.
2. Open the bug to the public
3. Coordinate the submission of the patch. The fix should be fast tracked as it has already been peer reviewed.
4. When the commit has been merged into the code an announcement must be sent individually to the following mailing lists: [email protected], [email protected]. 

#### Post-disclosure

Post disclosure the standard development process applies. Some optional additional tasks that the security team could undertake would be:

 - Convert the advisory publication to CVRF format and publish on a separate CVE stream
 - Calculate the CVSS2 score for the flaw
 - Determine the appropriate CWE for this flaw
 - Write an automated reproducer of the flaw and add it to the regression tests
 - Write an static analysis / lint rule to detect the pattern that lead to the flaw
 - Ensure the correct CVE is listed in the release notes for the next version of the affected product.
 


### Handling public security issues

#### What is considered public?
 - Any comment on a public forum, whether it be a mailing list, irc, twitter, or news group, that discloses the details of the flaw. 
 - Any commit or review comment that indicates that the change may be security related. 

#### Public security issue workflow

There will be occasions where the vulnerability management workflow process is either not followed, or at some stage a party leaks the details of the flaw. In these cases the following workflow is applicable.

```flow

public_security_issue=>start: A public security 
issue was identified
previously_private=>condition: Was the issue 
previously private? 
open_bug=>operation: Open the bug as public
bug_tracker_exists=>condition: Does a bug tracker 
exist for this issue?
create_bug_tracker=>operation: Create a bug tracker
confirmed_leaked=>operation: Add a confirmed-leaked 
statement to bug
confirmed_public=>operation: Add a confirmed-public 
statement to bug 
has_cve_been_assigned=>condition: Has a CVE been assigned?
request_cve=>operation: Request a CVE on 
<[email protected]>
impact_description=>operation: Develop advisory text
muster_developers=>operation: Get development commitment 
for high priority fix
monitor_fix=>operation: Monitor development status
fix_commited=>condition: Is the flaw fixed?
publish_advisory=>end: Publish the advisory information 
to <[email protected]>, 
<[email protected]>

public_security_issue->previously_private
previously_private(yes)->confirmed_leaked->open_bug->has_cve_been_assigned
has_cve_been_assigned(no)->request_cve->impact_description
has_cve_been_assigned(yes)->impact_description->muster_developers->monitor_fix->fix_commited
previously_private(no)->bug_tracker_exists
bug_tracker_exists(yes)->confirmed_public->request_cve
bug_tracker_exists(no)->create_bug_tracker->confirmed_public->request_cve
fix_commited(yes)->publish_advisory
fix_commited(no)->monitor_fix



```




### Communication 
#### Message format
All messages communicated formally by the OpenDaylight security team should be in a well formed YAML format. This includes statements in bugs, as well as published advisories. This approach will provide a foothold for future reporting, automation and conversion to more standardised formats such as [CVRF](http://www.icasi.org/cvrf-1.1).

#### Reception confirmation email

Upon reception of a security report the OpenDaylight security team needs to clearly indicate the expectation of how the issue will be handled. 

> Thank-you for your security report. 

>The OpenDaylight security team has created a private security bug to track this issue. Please provide us with your OpenDaylight bugzilla ID so we can add you to the tracker. All communications and decisions about how this issue will be handled will be recorded on the this bug to provide proper tracking.

> ```{{ bugzilla_tracker_url }}```

> Regards, 

> --
> ```{{ opendaylight_security_team_member }}``` 
> OpenDaylight Security Team


#### Confirmed private security issues

Clear instructions need to be provided to all parties involved with the fix as to how the issue needs to be fixed. When the flaw is confirmed, the following statement should be added to the bug by a member of the security team. 

> \#security-status: confirmed
> 
> This issue has been confirmed as a security vulnerability in ```{{ product }}``` and is to be fixed under the OpenDaylight embargoed security vulnerability process.  Please do not discuss or disclose details about this flaw prior to the agreed disclosure date (TBA). All decisions, discussions, and proposed patches and reviews are to be done via this tracking bug only. 

> If are you unsure of this process please refer to``` {{ opendaylight_security_process_url}}``` for more detailed instructions.

#### Confirmed public security issues

#####When an issue is leaked

> \#security-status: confirmed-leaked
> 
> This issue has been confirmed as a security vulnerability in ```{{ product }}```. Unfortunately the details of this flaw have been made public ```{{ reference_to_leak }}```. Therefore it cannot be fixed under the OpenDaylight embargoed security vulnerability process.  As this issue is now public it is important that the flaw is addressed in a timely manner. The OpenDaylight security team will ensure that a CVE is assigned for this issue.

##### When an issue was not reported privately 
> \#security-status: confirmed-public
> 
> This issue has been confirmed as a security vulnerability in ```{{ product }}```. As this issue was originally a public report it cannot be fixed under the OpenDaylight embargoed security vulnerability process.  As this issue is public it is important that the flaw is addressed in a timely manner. The OpenDaylight security team will ensure that a CVE is assigned for this issue.
  
#### Impact description

The impact description needs to provide an accurate description of the flaw, how it affects the product, and outline the version range that is affected. The impact description should be entered into the tracking bug and reviewed for correctness. 

> title: ```{{ impact description title }}```

> reporters: 
> &nbsp;&nbsp;&nbsp;&nbsp;- name: ```{{ reporter_name }}```
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  company: ```{{ reporter_company }}```

> affects:
&nbsp;&nbsp;&nbsp;&nbsp;- product:  ```{{ product }}```
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; version: ```{{ version_range }}```

> risk-assessment:
> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; impact-rating: ```{{ impact_rating}}```

> description: >
> &nbsp;&nbsp;&nbsp;&nbsp;```{{ reporter_name }}``` from ```{{ reporter_company }}``` 
> &nbsp;&nbsp;&nbsp;&nbsp;reported a vulnerability in ```{{ product }}``` ....
>

Version
:	The version string must explicitly indicate the range of products affected by the flaw. 
For example:  ```"2.1.2=>3.1.0"```
> **TBD**: [This approach](https://github.com/victims/victims-cve-db#version-string-common) may be more versatile. 

Risk Assessment
:	The security team should provide a judgement call for the severity of the issue for the most common use case of the project. Suggested impact rating categories:

      - **Critical**: This rating is given to flaws that could be easily exploited by a remote unauthenticated attacker and lead to system compromise (arbitrary code execution) without requiring user interaction. These are the types of vulnerabilities that can be exploited by worms. Flaws that require an authenticated remote user, a local user, or an unlikely configuration are not classed as Critical impact.
      
      - **Important**: This rating is given to flaws that can easily compromise the confidentiality, integrity, or availability of resources. These are the types of vulnerabilities that allow local users to gain privileges, allow unauthenticated remote users to view resources that should otherwise be protected by authentication, allow authenticated remote users to execute arbitrary code, or allow local or remote users to cause a denial of service.

      - **Moderate**: This rating is given to flaws that may be more difficult to exploit but could still lead to some compromise of the confidentiality, integrity, or availability of resources, under certain circumstances. These are the types of vulnerabilities that could have had a Critical impact or Important impact but are less easily exploited based on a technical evaluation of the flaw, or affect unlikely configurations.
	  
      - **Low**: This rating is given to all other issues that have a security impact. These are the types of vulnerabilities that are believed to require unlikely circumstances to be able to be exploited, or where a successful exploit would give minimal consequences.
> **Note**: Formal methods such as [CVSS](http://www.first.org/cvss) may follow. 

Description
: The description must endeavour to accurately depict the nature of the flaw. Information that should be included must indicate the attack vector that is exposed by the flaw and the initial access level required by the attacker. Where applicable advice on how an operator may audit for abuse of the flaw within their environment.

#### CVE Request

To ensure proper traceability a CVE identifier needs to be requested from a CNA. An email requesting a CVE should be sent to either <[email protected]> or <[email protected]>. The email must be GPG-signed and GPG-encrypted.

> A vulnerability was discovered in OpenDaylight (see below). In order
> to ensure full traceability, we need a CVE number assigned that we can
> attach to private and public notifications. Please treat the following
> information as confidential until further public disclosure.
> 
> ```{{ impact_description }}```
> 
> Thanks in advance,
> 
> --  
> ```{{ opendaylight_security_team_member }}```
> OpenDaylight security team

#### Advanced notification

In accordance with a [coordinated disclosure model](http://en.wikipedia.org/wiki/Full_disclosure_%28computer_security%29#Coordinated_disclosure), large operators or vendors selling a derivative of OpenDaylight software should be given advanced notification of security issues to patch their products prior to making the details of the flaw public. A timeline of 3-5 working days should be allowed for stakeholders to assess the impact on their products and services. Anyone who leaks an issue on purpose, or repeatedly leaks issues accidentally, will be excluded from future advanced notification.

> This is an advance warning of a vulnerability discovered in OpenDaylight,
> to give you, as downstream stakeholders, a chance to coordinate the
> release of fixes and reduce the vulnerability window. Please treat the
> following information as confidential until the proposed public
> disclosure date.
> 
> ```{{ impact_description }}```
> 
> Proposed patch: See attached patches. Unless a flaw is discovered in
> them, these patches will be merged to ```{{ branches }}``` on the public
> disclosure date.
> 
> CVE: ```{{ cve_id }}```
> 
> Proposed public disclosure date/time: ```{{ disclosure_date }}```. Please do
> not make the issue public (or release public patches) before this
> coordinated embargo date.
> 
> Regards,
> 
> -- 
> ```{{ opendaylight_security_team_member }}```
>  OpenDaylight Security Team


#### Advisory

The advisory notification builds on the existing impact description however it includes all the relative details of the fix. Each advisory should be given a unique identifier. This will be of the format ```<year>-<seq>```. Where _seq_ is a number that is incremented for each advisory issued for a given year.

> opendaylight-advisory: ```{{ odsa_id }}```
> cve: ```{{cve_id }}```
> advisory-date: ```{{ date_announced }}```

> ```{{ impact_description }}```

> changes:
> \# ```{{ release_name }}```
  &nbsp;&nbsp;- branch: ```{{ branch }}```
&nbsp;&nbsp;&nbsp; commit: ```{{ commit_hash }}```
&nbsp;&nbsp;&nbsp;  review: https://git.opendaylight.org/gerrit/#/c/```{{review_id}}```
>

> release-notes: >
> &nbsp;&nbsp;&nbsp;&nbsp; This fix will be included in the ```{{ milestone }}``` development milestone 
> &nbsp;&nbsp;&nbsp;&nbsp; and in a future ```{{ next_stable }}``` release.

> bug-tracker:  https://bugs.opendaylight.org/show_bug.cgi?id=```{{ bugzilla_id }}```

> -- 
> ```{{ opendaylight_security_team_member }}```
> OpenDaylight Security Team

#### Statement for non-security issues

In the cases where a potential security flaw has been reported but the OpenDaylight security team have determined that it is not to be fixed under the embargoed security process a statement indicating why this decision has been made. 

> \#security-status: wontfix
> statement:>
> &nbsp;&nbsp;&nbsp;&nbsp;The OpenDaylight security team has analysed this report and determined 
> &nbsp;&nbsp;&nbsp;&nbsp; that it is not a security issue. ```{{ reason }}```
> 
>  &nbsp;&nbsp;&nbsp;&nbsp;This bugs privacy status will now be changed to public, and the bug should 
>  &nbsp;&nbsp;&nbsp;&nbsp;be fixed following the normal development process. We would like to thank 
>  &nbsp;&nbsp;&nbsp;&nbsp;```{{ reporter }}``` for bringing this issue to our attention.


#### Information to include in commit message

The commit message for a vulnerability fix should include the following tag on a line by itself:
> \#security-fix: ```{{ cve_id }}```


##Roadmap

### Action Items

Topic | Assignee | Description
-|-|-
infrastructure | unassigned | Create a private mailing list for security team
infrastructure | unassigned | Enable private bugs in bugzilla
infrastructure | unassigned | Create a public page indicating contact information for the security team. This information must include the public GPG keys for each member of the security team. 
documentation | unassigned | Create a public page detailing the vulnerability management process and how to report security problems to OpenDaylight
documentation | unassigned | Create a public document indicating the security status of each OpenDaylight project.
documentation | unassigned | Document the expectations around the audit required for projects to receive 'security supported' status. This might include things like attack surface, dependency analysis, or just how to record the audit results. 
documentation | unassigned | Create a single page listing the CVE's addressed by each release of a OpenDaylight products. ([similar to this](http://httpd.apache.org/security/vulnerabilities_24.html))
organizational | unassigned | Form the security team. Decide when an how often meetings will be held. 
organizational | unassigned | Establish a list of downstream stakeholders that should be eligible for advanced notification of security issues. Inform them of this security process and communicate the expectations. Elicit feedback.
communication | unassigned | Ensure the new security process is announce on all major mailing lists.
future_work | unassigned | Work on automating the process to reduce human error
future_work | unassigned | Automate the mining of advisory information to allow for analysis of security landscape for each security supported project
future_work | unassigned | Automatically export advisory data in the standardized CVRF  




> Written with [StackEdit](https://stackedit.io/).