Difference between revisions of "2016-bidding/security coordination and tools"
|(One intermediate revision by the same user not shown)|
|Line 54:||Line 54:|
= Effort =
= Effort =
Bids planning a total effort of 24 Person Months/year would allow these services and activities to be addressed appropriately.
Bids planning a total effort of 24Person Months/year would allow these services and activities to be addressed appropriately.
Latest revision as of 17:30, 20 October 2016
|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|EGI Core services menu:||Services PHASE I •||Services PHASE II •||Services PHASE III •||Bids •||Payments •||Travel procedure •||Performance|
Go back to the EGI Core Activities Bidding page.
- Service name: Security coordination and security tools
Security is recognised as an important aspect of e-Infrastructures and requires coordination between the EGI participants at various levels, in particular for the prevention and handling of incidents.
To keep a distributed infrastructure secure there is need for a coordination activity of the security effort at NGI and resource center level, and for tools that automatically test the EGI sites for vulnerabilities. The activity ensures the central coordination of security activities, including incident response, vulnerabilities handling and security policies development.
The security coordination activities must liaise with the resource providers (~40 among NGIs and EIROS) the resource centres (~300) and oversee the technologies used in the production infrastructure, for example: O.S. Platforms, HTC, Cloud, Storage, AAI capabilities. Security coordination will have to liaise with the equivalent activities in other e-infrastructures
The service includes the following components.
- Security Operations Coordination - Central coordination of the security activities ensures that policies, operational security, and maintenance are compatible among all partners, improving availability and lowering access barriers for use of the infrastructure. This coordination ensures that incidents are promptly and efficiently handled, that common policies are followed by providing services such as security monitoring, and by training and dissemination with the goal of improving the response to incidents.
- Security Policy Coordination - Security policy development covers diverse aspects, including operational policies (agreements on vulnerability management, intrusion detection and prevention, regulation of access, and enforcement), incident response policies (governing the exchange of information and expected actions), participant responsibilities (including acceptable use policies, identifying users and managing user communities), traceability, legal aspects, and data protection. Since research is global, such policies must be coordinated with peer infrastructures in Europe and elsewhere, such as PRACE, Open Science Grid, XSEDE, and like efforts in the Asia Pacific.
- Security Incident Response Coordination - Coordination of incident response activities in collaboration with the Incident Response Task Force. The primary responsibility for basic incident response and forensics still lies with each NGI, while the EGI Global IRTF will coordinate incident response and information exchange. For complex multi-site incidents and in cases where advanced forensics is needed, the EGI Global IRTF will step in and take an active part, to protect the continued integrity of the EGI infrastructure as a whole. Validation of EGI Global incident response capability is done by coordinating security service challenges that both assess readiness of infrastructure operations and verify adequate traceability features in the software used. This task will also liaise with other CSIRTs.
- Software Vulnerability Group Coordination - The Software Vulnerability Group aims to eliminate existing software vulnerabilities from the deployed infrastructure and prevent the introduction of new ones, and runs a process for handling software vulnerabilities reported. This depends on investigation and risk assessment by a collaborative team drawn from technology providers and other security groups, known as the Risk Assessment Team (RAT).
- International Grid Trust Federation (IGTF) and EUGridPMA - A common authentication trust domain is required to persistently identify all EGI participants. This task is about the representation of EGI in IGTF and EUGridPMA. This representation will bring operational and policy needs of EGI to the attention of the PMA, bring issues raised by the PMA to the attention of the appropriate groups within EGI, and keep the EGI Council informed of progress and policies of the EUGridPMA. This task is also responsible for the coordination of the provision of EGI versions of the IGTF Certification Authority distributions as required by the EGI Council.
In particular the activity will have to liaise with the following entities:
- NGI and EIROs security teams. In the hierarchical operatioanl structure of EGI most of the communications go from EGI to the Operations Centres, and then from the Operations Centres to the Resource Centres.
- Resource Centres security teams. To ensure prompt reaction and support in case of security incident or critical violation of security policies.
- Other European and international e-infrastructures and research infrastructure. The liaison must be direct peer to peer and in the context of security initiatives such as WISE as an example, respectively to tackle specific topics or to develop a collaboration framework for security.
- Cross infrastructure policy groups, such as for example FIM4R and REFEDS.
The provisioning of this activity includes the operations and maintenance of the operational tools that support security, namely:
- Security Monitoring - the activity should provide monitoring services to check for security vulnerabilities and other security-related problems in the EGI production infrastructure. Monitoring uses ad-hoc probes implemented to address specific security issues as well as generic probes used to gather security-related information. The main features are:
- Monitor a range security relevant assets like for example: CRLs, file system permissions and vulnerable file permissions
- Monitor and check the software packages deployed in the services of the production infrastructure and the status of patching security vulnerability by deploying relevant software updates.
- Incident Reporting Tool - ticketing system for tracking of incident reporting activities.
- Tools for Security Service Challenge support - Security challenges are a mechanism to check the compliance of sites/NGIs/EGI with security requirements. Runs of Security Service Challenges need a set of tools that are used during various stages of the runs.
- Daily support activities
- Support through the EGI helpdesk to users and service providers.
- Support through email@example.com for the incident handling.
- Support hours eight hours a day , Monday to Friday – excluding public holidays of the hosting organization.
- Security trainings will be provided to the EGI stakeholders, for example during the major EGI events.
Service level targets
- Minimum availability/reliability: 90%/90%
- Response to incident records in GGUS within support hours: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)
Bids planning a total effort of 24-30 Person Months/year would allow these services and activities to be addressed appropriately.