Identity and Access Management
Book
MidPoint
- Compliance
  - ISO 27001
    - 5.1
    - 5.2
    - 5.3
    - 5.4
    - 5.5
    - 5.6
    - 5.7
    - 5.8
    - 5.9
    - 5.10
    - 5.11
    - 5.12
    - 5.13
    - 5.14
    - 5.15
    - 5.16
    - 5.17
    - 5.18
    - 5.19
    - 5.20
    - 5.21
    - 5.22
    - 5.23
    - 5.24
    - 5.25
    - 5.26
    - 5.27
    - 5.28
    - 5.29
    - 5.30
    - 5.31
    - 5.32
    - 5.33
    - 5.34
    - 5.35
    - 5.36
    - 5.37
    - 6.1
    - 6.2
    - 6.3
    - 6.4
    - 6.5
    - 6.6
    - 6.7
    - 6.8
    - 7.1
    - 7.2
    - 7.3
    - 7.4
    - 7.5
    - 7.6
    - 7.7
    - 7.8
    - 7.9
    - 7.10
    - 7.11
    - 7.12
    - 7.13
    - 7.14
    - 8.1
    - 8.2
    - 8.3
    - 8.4
    - 8.5
    - 8.6
    - 8.7
    - 8.8
    - 8.9
    - 8.10
    - 8.11
    - 8.12
    - 8.13
    - 8.14
    - 8.15
    - 8.16
    - 8.17
    - 8.18
    - 8.19
    - 8.20
    - 8.21
    - 8.22
    - 8.23
    - 8.24
    - 8.25
    - 8.26
    - 8.27
    - 8.28
    - 8.29
    - 8.30
    - 8.31
    - 8.32
    - 8.33
    - 8.34
Identity Connectors
Support
Trainings
Evolveum
Community
Library
Case Studies
Talks
Glossary
Frequently Asked Questions
About

ISO/IEC 27001 Control 5.30: ICT readiness for business continuity

Control

ICT readiness should be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements.

Necessity of MidPoint

MidPoint is optional for implementation of this control.

Implementation of this control without midPoint is feasible. However, midPoint provides considerable advantages for implementation of this control, making the implementation more efficient and reliable.

Implementation Overview

MidPoint can be used to quickly prepare replacement system in case of disruption. Pre-configure emergency access control can be used during incident response.

Implementation Details

MidPoint is designed to work with systems (identity resources) that are not constantly available. Operations are re-tried, resource can be explicitly configured for maintenance mode, synchronization capability can be used to restore data consistency. Provisioning consistency capability of midPoint automatically corrects all inconsistencies it discovers, which can be used to gradually recover from disruption. Auto-scaling capability can provide resilience to unexpected load peaks. Policy-driven RBAC mechanism can be used to activate pre-configure emergency access control during disruption, providing controlled and panic-free elevation of privileges for responders. Simulation can be used to validate such pre-configured privileges and policies and their effect on the system, to make sure they can be used to maintain critical business processes following interruption or failure. Certification campaigns can be used to make sure emergency privileges are reviewed at regular intervals - both assignment of emergency privileges to users, as well as content of the emergency roles. Application inventory provides essential data on systems during failure, e.g determining number of users affected by the disruption. Should there be a need to create a replacement system during disruption, midPoint RBAC mechanisms together with efficient provisioning engine can be used to quickly and automatically grant access to the replacement system, maintaining appropriate access levels for individual users. E.g. midPoint can quickly provision access to a new application in case that an existing cloud application is disrupted. MidPoint identity repository contains copies of identity data, which can be used to quickly restore the data to any application. This is further supplemented by organizational structure, personas and the dynamic rules of policy-driven RBAC, which together form a flexible policy platform to quickly populate replacement systems. Replacement system can be either provisioned automatically, using ConnId identity connectors, or manually/semi-manually using midPoint built-in manual connector. Live synchronization can be used to keep replacement systems updated with the latest identity data, as a copy from other systems.

Implementation Notes

MidPoint has a built-in high-availability features.
Unavailability of MidPoint does not mean unavailability of identity and access management capabilities. MidPoint is designed to provision changes to identity resources, allowing resources to operate independently. Unavailability of midPoint means limitation of identity management capabilities, however it does not usually limit operational capabilities of applications.

Rationale

MidPoint can be used as supporting tool for business continuity.

Was this page helpful?

YES NO

Thanks for your feedback