The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Search results
Jump to navigation
Jump to search
Page title matches
- {{svg-header}} == Software Vulnerability Group (SVG) view and responsibilities concerning issue handling ==2 KB (313 words) - 10:40, 29 April 2016
Page text matches
- {{svg-header}} ...G Risk Assessment Team or "RAT" is the group of people who co-ordinate the SVG issue handling process and along with the Deployment Expert Group (DEG) car2 KB (363 words) - 20:40, 19 October 2020
- {{svg-header}} This provides information on the view and responsibilities of those deploying the software, useful to both NGIs a1 KB (239 words) - 11:12, 29 April 2016
- {{svg-header}} == Software Vulnerability Group (SVG) view and responsibilities concerning issue handling ==2 KB (313 words) - 10:40, 29 April 2016
- {{svg-header}} ...r Security Incident Report Team [[EGI CSIRT:Main_Page|EGI-CSIRT]] point of view.2 KB (323 words) - 18:42, 1 November 2010
- {{svg-header}} ...nit, who distribute software in the UMD will need to interact with the EGI SVG.2 KB (303 words) - 18:13, 1 November 2010
- {{svg-header}} Guidelines on SVG's risk categories are at:3 KB (529 words) - 15:20, 28 April 2016
- {{svg-header}} ...**UPDATE** [TLP:WHITE] CRITICAL risk Vulnerability concerning dCache [EGI-SVG-2020-16939]5 KB (747 words) - 17:13, 14 January 2021
- {{svg-header}} Title: EGI SVG Advisory [TLP:AMBER] Up to 'HIGH' risk DIRAC configuration -6 KB (861 words) - 17:57, 18 July 2016
- | EGI SVG Monthly meeting | EGI SVG Monthly meeting8 KB (1,247 words) - 18:43, 6 January 2015
- * various SVG advisories released * New view aggregating all region charts for InterNGI reports (NGI/COUNTRY).5 KB (796 words) - 18:17, 6 January 2015
- * Recommendations and issues found by the [[SVG:SVG | Software Vulnerability Group]] ...uality Criteria. The metric considers also security incidents found by the SVG.15 KB (2,364 words) - 16:13, 23 March 2016
- ...e plan also states which software packages that have been assessed so far. SVG will improve the handling of software vulnerabilities in the EGI RT to impr ...or NGIs that have currently gone through this process. xGUS – the GGUS NGI view – is now deployed in production by several NGIs.23 KB (3,456 words) - 16:19, 6 January 2015
- ...graph should include: EGI CSIRT, security training, security drills, IRTF, SVG and if you want SPG --> ====Software Vulnerability (SVG) coordination====45 KB (6,684 words) - 16:17, 6 January 2015
- ...o allow staff to resolve any issues detected. Members of the EGI CSIRT can view all details and if necessary, follow up with sites to assist them to addres ...nsible for developing security policies. The Software Vulnerability Group (SVG) aims to eliminate existing software vulnerabilities from the deployed infr32 KB (4,677 words) - 23:07, 24 December 2014
- ...o allow staff to resolve any issues detected. Members of the EGI CSIRT can view all details and if necessary, follow up with sites to assist them to addres ...nsible for developing security policies. The Software Vulnerability Group (SVG) aims to eliminate existing software vulnerabilities from the deployed infr30 KB (4,383 words) - 23:06, 24 December 2014
- *'''MVC '''- Model-View-Control * '''SVG''' - Software Vulnerabity Group26 KB (3,474 words) - 14:58, 9 November 2016
- rc libevview1 2.28.1-0ubuntu1.3 GNOME document viewer view library rc libevview2 2.30.3-0ubuntu1.2 GNOME document viewer view library511 KB (47,465 words) - 23:41, 2 December 2013