Difference between revisions of "Dynamic DNS Availability and Continuity Plan"
(12 intermediate revisions by 2 users not shown) | |||
Line 14: | Line 14: | ||
|- | |- | ||
! scope="row"| Risks assessment | ! scope="row"| Risks assessment | ||
| | | 2021-10 | ||
| | | 2022-10 | ||
|- | |- | ||
! scope="row"| Av/Co plan and test | ! scope="row"| Av/Co plan and test | ||
Line 24: | Line 24: | ||
previous plans are collected here: | previous plans are collected here: https://documents.egi.eu/document/3855 | ||
= Availability requirements and performances = | = Availability requirements and performances = | ||
In the OLA it was agreed the following performances targets, on a monthly basis: | In the OLA it was agreed the following performances targets, on a monthly basis: | ||
*Availability: | *Availability: 90% | ||
*Reliability: | *Reliability: 90% | ||
Other availability requirements: | |||
* the service | * Users of the service are authenticated through EGI Check-in | ||
* The service is accessible via CLI and/or | * The service is accessible via CLI and/or web UI at https://nsupdate.fedcloud.eu/ | ||
The service availability is regularly tested by nagios probes (https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_eu.egi.cloud.dyndns) | |||
The performances reports in terms of Availability and Reliability are produced by [http://egi.ui.argo.grnet.gr/egi/OPS-MONITOR-Critical ARGO] on an almost real time basis and they are also periodically collected into the [https://documents.egi.eu/public/ShowDocument?docid=2324 Documentation Database]. | The performances reports in terms of Availability and Reliability are produced by [http://egi.ui.argo.grnet.gr/egi/OPS-MONITOR-Critical ARGO] on an almost real time basis and they are also periodically collected into the [https://documents.egi.eu/public/ShowDocument?docid=2324 Documentation Database]. | ||
Over the past years, the | Over the past years, the Dynamic DNS service hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.'' | ||
= Risks assessment and management = | = Risks assessment and management = | ||
For more details, please look at the (google spreadsheet link). We will report here a summary of the assessment. | For more details, please look at the (google spreadsheet link). We will report here a summary of the assessment. | ||
Line 65: | Line 61: | ||
| Hosting services on different cloud sites, Monitoring services via ARGO | | Hosting services on different cloud sites, Monitoring services via ARGO | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | no downtime unless both Cloud sites hosting servies are down, up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 73: | Line 69: | ||
| Hosting services on different cloud sites, Monitoring services via ARGO | | Hosting services on different cloud sites, Monitoring services via ARGO | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 81: | Line 77: | ||
| Automation, clear documentation and procedure | | Automation, clear documentation and procedure | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 89: | Line 85: | ||
| Hosting services on different cloud sites, Monitoring services via ARGO | | Hosting services on different cloud sites, Monitoring services via ARGO | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 105: | Line 101: | ||
| Hosting services on different cloud sites, Monitoring services via ARGO | | Hosting services on different cloud sites, Monitoring services via ARGO | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | no downtime unless both Cloud sites hosting servies are down, up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 113: | Line 109: | ||
| Firewall, minimal external access, regular software update, site IDS | | Firewall, minimal external access, regular software update, site IDS | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | up to 8 hours for DNS server, 2 days for nsupdate server | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|- | |- | ||
Line 119: | Line 115: | ||
| (D)DOS attack. The service is unavailable because of a coordinated DDOS. | | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | ||
| nsupdate server, DNS servers | | nsupdate server, DNS servers | ||
| Limiting request rate, detecting and | | Limiting request rate, detecting and responding DDOS attack by site IDS | ||
| style="background: green"| Low | | style="background: green"| Low | ||
| | | No downtime | ||
| the measures already in place are considered satisfactory and risk level is acceptable | | the measures already in place are considered satisfactory and risk level is acceptable | ||
|} | |} | ||
== Outcome == | == Outcome == | ||
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory | The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory | ||
== Additional information == | == Additional information == | ||
* The provider has got procedures for the several countermeasures to invoke in case of risk occurrence | |||
procedures for the several countermeasures to invoke in case of risk occurrence | * The Availability targets don't change in case the plan is invoked. | ||
* Recovery requirements: | |||
** Maximum tolerable period of disruption (MTPoD) (the maximum amount of time that a service can be unavailable or undelivered after an event that causes disruption to operations, before its stakeholders perceive unacceptable consequences): 2 days | |||
** Recovery time objective (RTO) (the acceptable amount of time to restore the service in order to avoid unacceptable consequences associated with a break in continuity (this has to be less than MTPoD)): 1 day | |||
** Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 1 day | |||
*Maximum tolerable period of disruption (MTPoD) (the maximum amount of time that a service can be unavailable or undelivered after an event that causes disruption to operations, before its stakeholders perceive unacceptable consequences): | * Approach for the return to normal working conditions as reported in the risk assessment. | ||
*Recovery time objective (RTO) (the acceptable amount of time to restore the service in order to avoid unacceptable consequences associated with a break in continuity (this has to be less than MTPoD)): | * The support unit Dynamic DNS shall be used to report any incident or service request | ||
*Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): | * The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it. | ||
The support unit | |||
The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it. | |||
= Availability and Continuity test = | = Availability and Continuity test = | ||
<p style="color: blue> | <p style="color: blue> | ||
Line 168: | Line 157: | ||
|- | |- | ||
| | | | ||
| | | Alessandro Paolini | ||
| | | 2021-10-27, 2021-12-09 | ||
| | | Risk assessment completed; added other information; details of the recovery test to be agreed | ||
|- | |- | ||
| | | |
Latest revision as of 10:53, 9 December 2021
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Back to main page: Services Availability Continuity Plans
Introduction
This page reports on the Availability and Continuity Plan for the Dynamic DNS and it is the result of the risks assessment conducted for this service: a series of risks and treats has been identified and analysed, along with the correspondent countermeasures currently in place. Whenever a countermeasure is not considered satisfactory for either avoiding or reducing the likelihood of the occurrence of a risk, or its impact, it is agreed with the service provider a new treatment for improving the availability and continuity of the service. The process is concluded with an availability and continuity test.
Last | Next | |
---|---|---|
Risks assessment | 2021-10 | 2022-10 |
Av/Co plan and test |
previous plans are collected here: https://documents.egi.eu/document/3855
Availability requirements and performances
In the OLA it was agreed the following performances targets, on a monthly basis:
- Availability: 90%
- Reliability: 90%
Other availability requirements:
- Users of the service are authenticated through EGI Check-in
- The service is accessible via CLI and/or web UI at https://nsupdate.fedcloud.eu/
The service availability is regularly tested by nagios probes (https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_eu.egi.cloud.dyndns)
The performances reports in terms of Availability and Reliability are produced by ARGO on an almost real time basis and they are also periodically collected into the Documentation Database.
Over the past years, the Dynamic DNS service hadn't particular Av/Co issues highlighted by the performances that need to be further investigated.
Risks assessment and management
For more details, please look at the (google spreadsheet link). We will report here a summary of the assessment.
Risks analysis
Risk id | Risk description | Affected components | Established measures | Risk level | Expected duration of downtime / time for recovery | Comment |
---|---|---|---|---|---|---|
1 | Service unavailable / loss of data due to hardware failure | nsupdate server, DNS servers | Hosting services on different cloud sites, Monitoring services via ARGO | Low | no downtime unless both Cloud sites hosting servies are down, up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
2 | Service unavailable / loss of data due to software failure | nsupdate server, DNS servers | Hosting services on different cloud sites, Monitoring services via ARGO | Low | up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
3 | service unavailable / loss of data due to human error | nsupdate server, DNS servers | Automation, clear documentation and procedure | Low | up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
4 | service unavailable for network failure (Network outage with causes external of the site) | nsupdate server, DNS servers | Hosting services on different cloud sites, Monitoring services via ARGO | Low | up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
5 | Unavailability of key technical and support staff (holidays period, sickness, ...) | nsupdate server, DNS servers | Getting funds for service operation, SLA, OLA | Low | the measures already in place are considered satisfactory and risk level is acceptable | |
6 | Major disruption in the data centre. Fire, flood or electric failure for example | nsupdate server, DNS servers | Hosting services on different cloud sites, Monitoring services via ARGO | Low | no downtime unless both Cloud sites hosting servies are down, up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
7 | Major security incident. The system is compromised by external attackers and needs to be reinstalled and restored. | nsupdate server, DNS servers | Firewall, minimal external access, regular software update, site IDS | Low | up to 8 hours for DNS server, 2 days for nsupdate server | the measures already in place are considered satisfactory and risk level is acceptable |
8 | (D)DOS attack. The service is unavailable because of a coordinated DDOS. | nsupdate server, DNS servers | Limiting request rate, detecting and responding DDOS attack by site IDS | Low | No downtime | the measures already in place are considered satisfactory and risk level is acceptable |
Outcome
The level of all the identified risks is acceptable and the countermeasures already adopted are considered satisfactory
Additional information
- The provider has got procedures for the several countermeasures to invoke in case of risk occurrence
- The Availability targets don't change in case the plan is invoked.
- Recovery requirements:
- Maximum tolerable period of disruption (MTPoD) (the maximum amount of time that a service can be unavailable or undelivered after an event that causes disruption to operations, before its stakeholders perceive unacceptable consequences): 2 days
- Recovery time objective (RTO) (the acceptable amount of time to restore the service in order to avoid unacceptable consequences associated with a break in continuity (this has to be less than MTPoD)): 1 day
- Recovery point objective (RPO) (the acceptable latency of data that will not be recovered): 1 day
- Approach for the return to normal working conditions as reported in the risk assessment.
- The support unit Dynamic DNS shall be used to report any incident or service request
- The providers can contact EGI Operations via ticket or email in case the continuity plan is invoked, or to discuss any change to it.
Availability and Continuity test
The proposed A/C test will focus on a recovery scenario: the service is supposed to have been disrupted and needs to be reinstalled from scratch. Typically this covers the risks 1,2, and 7. The last backup of the data will be used for restoring the service, verifying how much information will be lost, and the time spent will be measured.
Performing this test will be useful to spot any issue in the recovery procedures of the service.
Test details
Test outcome
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
Alessandro Paolini | 2021-10-27, 2021-12-09 | Risk assessment completed; added other information; details of the recovery test to be agreed | |