Difference between revisions of "SVG:Software Providers View"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{svg-header}} | {{svg-header}} | ||
{{under construction}} | |||
== Software providers agree to an SLA == | |||
In order that their software is included in the EGI UMD, software providers agree to a Service Level Agreement (SLA). For members of EGI, this can be read from | |||
In summary, they agree: | |||
* Suspected vulnerabities found in their software are handled using the EGI SVG issue handling process | |||
* To provide contact details | |||
* To respond when asked by SVG as soon as possible - or at least within 2 working days | |||
* To co-operate to ensure that if they find a vulnerability in their own software, they fix in a timely manner and ensure that the new version is available in the UMD for an appropriate amount of time prior to releasing information on it | |||
{{svg-issue-views}} | {{svg-issue-views}} |
Revision as of 17:14, 28 October 2010
Main page | Software Security Checklist | Issue Handling | Advisories | Notes On Risk | Advisory Template | More |
Software Providers View
This page is under construction. |
Software providers agree to an SLA
In order that their software is included in the EGI UMD, software providers agree to a Service Level Agreement (SLA). For members of EGI, this can be read from
In summary, they agree:
- Suspected vulnerabities found in their software are handled using the EGI SVG issue handling process
- To provide contact details
- To respond when asked by SVG as soon as possible - or at least within 2 working days
- To co-operate to ensure that if they find a vulnerability in their own software, they fix in a timely manner and ensure that the new version is available in the UMD for an appropriate amount of time prior to releasing information on it
| Issue Handling Summary | Reporters | SVG View | Software Providers | EGI MW Unit | Deployment | Notes on Risk |