|
+Resilient Data Backup Architecture |
Resilient Data Backup ArchitectureDescriptionMechanisms exist to maintain a secure, immutable backuparchitecture. Possible Solutions & ConsiderationsMicro-Small Business (<10 staff) / BLS Firm Size Classes 1-2∙ Cloud backup with immutability/object lock (e.g., Backblaze B2, Wasabi, AWS S3 Object Lock)∙ Offline backup media rotated off-site Small Business (10-49 staff) / BLS Firm Size Classes 3-4∙ Cloud backup with object lock (e.g., AWS S3 Object Lock, Azure Immutable Blob)∙ Backup software with immutable repositories (e.g., Veeam Hardened Repository) ∙ Separate backup administrator credentials with MFA Medium Business (50-249 staff) / BLS Firm Size Classes 5-6∙ Backup platform with immutable storage (e.g., Veeam, Rubrik, Cohesity)∙ Isolated backup network and credentials ∙ Annual immutability and restore testing Large Business (250-999 staff) / BLS Firm Size Classes 7-8∙ Enterprise backup platform with immutable storage (e.g., Veeam, Rubrik, Cohesity, Commvault)∙ Air-gapped or logically vaulted backup copy ∙ Privileged Access Management (PAM) for backup administration Enterprise (> 1,000 staff) / BLS Firm Size Class 9∙ Enterprise backup platform with immutable storage (e.g., Commvault, Rubrik, Cohesity, Dell PowerProtect Cyber Recovery)∙ Isolated recovery environment / cyber vault ∙ PAM-controlled backup administration with MFA ∙ Automated immutability verification and restore testing SCR-CMMLevel 0 Not PerformedPractices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.Level 1 Performed InformallyBusiness Continuity & Disaster Recovery (BCD) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:▪ Policies, standards & procedures associated with BCD domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Contingency management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel develop limited Disaster Recovery Plans (DRP) to recover business-critical Technology Assets, Applications and/or Services (TAAS) and services. ▪ Recovery Time Objectives (RTOs) and/or Recovery Point Objectives (RPOs) are not formally planned for or resourced to meet. ▪ Backups are performed ad-hoc and focus on business-critical Technology Assets, Applications, Services and/or Data (TAASD). ▪ IT and/or cybersecurity personnel use a backup methodology (e.g., grandfather and father & son rotation) to create backups to support business needs (e.g., Recovery Time Objectives). ▪ Limited technologies exist to conduct full, incremental or differential backups (e.g., tape/disk, hybrid cloud or direct-to-cloud). ▪ Backups of sensitive/regulated data are cryptographically protected to prevent the unauthorized disclosure and modification of backup information. ▪ A random sampling of backups is tested at least annually to verify integrity and recoverability of backed up data. ▪ Backup copies of software or licenses/product keys are stored locally in a fire-rated container. Level 2 Planned TrackedBusiness Continuity & Disaster Recovery (BCD) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist:▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Business Continuity / Disaster Recovery (BC/DR)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ BC/DR may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Appropriate TAASD exist to conduct full, incremental and/or differential backups (e.g., tape/disk, hybrid cloud or direct-to-cloud). ▪ IT personnel configure business-critical Technology Assets, Applications and/or Services to transfer backup data to the alternate site(s) at a rate that is capable of meeting RTOs and RPOs. ▪ The backup methodology is sufficient to support RTOs and RPOs for critical business functions. ▪ IT personnel store backups in a secondary location, separate from the primary storage site (e.g., cloud-based storage). ▪ IT personnel perform a random sampling of backups is tested at least semi-annually to verify integrity and recoverability of backed up data. ▪ Backups for sensitive/regulated data are cryptographically protected (encrypted and integrity checked) to prevent the unauthorized disclosure and modification of backup information. ▪ IT personnel backup copies of business-critical software, licenses/keys and other security-related information to the alternate site. Level 3 Well DefinedBusiness Continuity & Disaster Recovery (BCD) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist:▪ Policies and standards associated with BCD domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with BCD domain capabilities are well-documented and kept current by process owners. ▪ A Business Continuity & Disaster Recovery (BC/DR) team, or similar function, is appropriately staffed and supported to implement and maintain BCD domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of BC/DR operations (e.g., BC/DR planning software, Disaster Recovery as a Service (DRaaS), Orchestration and Automation Tools). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with BCD domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). Level 4 Quantitatively ControlledUtilize SCR-CMM Level 3 criteria definitions:▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define. Level 5 Continuously ImprovingUtilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions:▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define. 1. Ħarsa ġenerali
1.1 Referenzi1.2 Rekwiżiti identifikati1.3 Regolamenti relatati2. Rekwiżiti identifikati
3. Regolamenti relatati
Kwistjonijiet marbuta
|