Difference between revisions of "SVG:General Advisory Template"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
<pre> | <pre> | ||
<add or delete sections as needed> | <add or delete sections as needed> | ||
< Choose proper TLP color > | |||
** WHITE information - Unlimited distribution allowed ** or | ** WHITE information - Unlimited distribution allowed ** or | ||
** GREEN information - Community wide distribution ** or | ** GREEN information - Community wide distribution ** or | ||
** AMBER information - Limited distribution ** | ** AMBER information - Limited distribution ** or | ||
** RED information - Personal for Named Recipients Only ** | |||
** see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions ** | |||
< Fill in advisory number, title, date, and URL(if WHITE)> | |||
< Title should be prepended by the RISK rating (e. g., CRITICAL, HIGH, ...)> | |||
< If applicable, a CVE number or the like should be included > | |||
< The title should be used as mail subject as well> | |||
EGI CSIRT ADVISORY [EGI-ADV-yyyymmdd] or | EGI CSIRT ADVISORY [EGI-ADV-yyyymmdd] or | ||
EGI SVG ADVISORY [EGI-SVG-yyyymmdd] | EGI SVG ADVISORY [EGI-SVG-yyyymmdd] | ||
Title: <Title | Title: <Title RISK - refer to any CVE number and include name software [EGI-ADV-YYYYMMDD] > | ||
Date: <date> | Date: <date yyyy-mm-dd> | ||
Updated: <date yyyy-mm-dd> | |||
<Put on Wiki for WHITE information only> | <Put on Wiki for WHITE information only> | ||
URL: | URL: https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts/<xxx>-yyyy-mm-dd or | ||
URL: | URL: https://wiki.egi.eu/wiki/SVG:Advisories/advisory-SVG-RT<number> | ||
Introduction | Introduction | ||
============ | ============ | ||
<Describe the reason for the issuing of this advisory - paragraph 3-5 sentences > | |||
< | < A vulnerability has been found in <xxx> software which is part of the <yyy> distribution.> | ||
<this could include - e.g. updated as patch available> | <this could include - e.g. updated as patch available> | ||
Line 34: | Line 45: | ||
<include EGI RT number for SVG/UMD issues> | <include EGI RT number for SVG/UMD issues> | ||
Line 46: | Line 59: | ||
<take care not to release anything useful to an attacker, unless it is already public, | <take care not to release anything useful to an attacker, unless it is already public, | ||
especially if you are sending it in WHITE> | especially if you are sending it in WHITE> | ||
<this should not be long> | |||
Line 51: | Line 67: | ||
============= | ============= | ||
<This issue has been assess as Critical/High/Moderate/Low by CSIRT or SVG as appropriate> | <This issue has been assess as Critical/High/Moderate/Low risk by the EGI CSIRT and/or EGI SVG | ||
Risk Assessment Team as appropriate> | |||
<if critical - include critical in title and e-mail title> | <if critical - include critical in title and e-mail title> | ||
Line 67: | Line 84: | ||
<Describe mitigation to carry out - this may be to run a script> | <Describe mitigation to carry out - this may be to run a script> | ||
< If possible, include either a script and/or include command lines> | |||
Line 86: | Line 105: | ||
<Immediately apply the mitigation described above to all user-accessible systems.> | <Immediately apply the mitigation described above to all user-accessible systems.> | ||
< | <Immediately apply vendor kernel updates when they become available.> | ||
<List vendors who have already announced patches> | |||
<Apply new version in EGI UMD> | <Apply new version in EGI UMD> | ||
<Sites are recommended to update relevant components.> | |||
<(For critical) All running resources MUST be either patched or otherwise have a | |||
work-around in place by yyyy-mm-dd T21:00+01:00. | |||
<7 calendar days - but if the date falls on a Friday, weekend, or common public holiday, | |||
make it the first working day after people are expected back> | |||
Line 94: | Line 124: | ||
====== | ====== | ||
<if applicable - person who discovers vulnerability> | This vulnerability was reported by <if applicable - person who discovers vulnerability> | ||
Line 100: | Line 130: | ||
========== | ========== | ||
<Any references to the vulnerability> | |||
<refer to any public disclosure> | <refer to any public disclosure> | ||
<e.g. Linux vendors info> | <e.g. Linux vendors info> |
Revision as of 18:33, 9 December 2010
Main page | Software Security Checklist | Issue Handling | Advisories | Notes On Risk | Advisory Template | More |
General Advisory Template
<add or delete sections as needed> < Choose proper TLP color > ** WHITE information - Unlimited distribution allowed ** or ** GREEN information - Community wide distribution ** or ** AMBER information - Limited distribution ** or ** RED information - Personal for Named Recipients Only ** ** see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions ** < Fill in advisory number, title, date, and URL(if WHITE)> < Title should be prepended by the RISK rating (e. g., CRITICAL, HIGH, ...)> < If applicable, a CVE number or the like should be included > < The title should be used as mail subject as well> EGI CSIRT ADVISORY [EGI-ADV-yyyymmdd] or EGI SVG ADVISORY [EGI-SVG-yyyymmdd] Title: <Title RISK - refer to any CVE number and include name software [EGI-ADV-YYYYMMDD] > Date: <date yyyy-mm-dd> Updated: <date yyyy-mm-dd> <Put on Wiki for WHITE information only> URL: https://wiki.egi.eu/wiki/EGI_CSIRT:Alerts/<xxx>-yyyy-mm-dd or URL: https://wiki.egi.eu/wiki/SVG:Advisories/advisory-SVG-RT<number> Introduction ============ <Describe the reason for the issuing of this advisory - paragraph 3-5 sentences > < A vulnerability has been found in <xxx> software which is part of the <yyy> distribution.> <this could include - e.g. updated as patch available> <include cve- number if one has been issued> <include EGI RT number for SVG/UMD issues> Details ======= <describe the problem, something about why it occurs, and the effect on sites> <take care not to release anything useful to an attacker, unless it is already public, especially if you are sending it in WHITE> <this should not be long> Risk Category ============= <This issue has been assess as Critical/High/Moderate/Low risk by the EGI CSIRT and/or EGI SVG Risk Assessment Team as appropriate> <if critical - include critical in title and e-mail title> Affected Software ================= <e.g. which version(s) of Linux are effected> <e.g. which middleware component is effected within gLite/ARC/Unicore/Globus/Other> Mitigation ========== <Describe mitigation to carry out - this may be to run a script> < If possible, include either a script and/or include command lines> Component Installation information ================================== <e.g. patch not yet available> <e.g. patch available from vendor for x system but not y> <e.g. pointer to UMD release > Recommendations =============== <as appropriate e.g.> <Immediately apply the mitigation described above to all user-accessible systems.> <Immediately apply vendor kernel updates when they become available.> <List vendors who have already announced patches> <Apply new version in EGI UMD> <Sites are recommended to update relevant components.> <(For critical) All running resources MUST be either patched or otherwise have a work-around in place by yyyy-mm-dd T21:00+01:00. <7 calendar days - but if the date falls on a Friday, weekend, or common public holiday, make it the first working day after people are expected back> Credit ====== This vulnerability was reported by <if applicable - person who discovers vulnerability> References ========== <Any references to the vulnerability> <refer to any public disclosure> <e.g. Linux vendors info> <any other info on the problem> Timeline <probably SVG/EGI UMD issues only> ======== Yyyy-mm-dd 2010-??-?? Vulnerability reported by <name1> WE NEED TO ASK HIM/HER BEFORE PUTTING HIS/HER NAME 2010-??-?? Acknowlegement from the EGI SVG to the reporter 2010-??-?? Software providers responded and involved in investigation 2010-??-?? Assessment by the EGI Software Vulnerability Group reported to the software providers 2010-??-?? Updated packages available <in the EGI UMD/other location> 2010-??-?? Public disclosure On behalf of the <EGI CSIRT / EGI CSIRT and SVG / EGI SVG as appropriate> ,
| RAT Issue Handling Instructions | RAT Issue Handling Templates | RAT Issue Handling Templates contd | SVG-CSIRT Critical Notes | Advisory Template |
| Issue Handling Summary | Reporters | SVG View | Software Providers | EGI MW Unit | Deployment | Notes on Risk |