Failure Response Plan for Protectimus On-Premise MFA Platform

In the event of a failure of the Protectimus On-Premise Platform, a quick and structured response is essential to minimize downtime and maintain security. This action plan in case of On-Premise Protectimus Platform failure outlines key failure scenarios, monitoring recommendations, recovery procedures, and preventive measures. By following these guidelines, administrators can efficiently detect, address, and prevent platform disruptions.

1. General Information

The Protectimus Two-Factor Authentication Platform is used in an on-premise configuration. It consists of the following main components:

• Database (DB);
• Application server and API.

These components can operate on a single server or be distributed across multiple machines. There is also the possibility of deploying a solution with a backup server or cluster for fault tolerance.

2. Possible Failure Scenarios

The main potential causes of failure for the Protectimus On-Premise Platform include:

• Database failure;
• Application server crash or malfunction;
• Network failure – no access to the API;
• Hardware failure.

Note: External attacks such as DDoS are not considered, as the platform does not have external access.

3. Monitoring Recommendations for Immediate Issue Detection

It is recommended to set up automatic monitoring (in the case of a cluster, each node must be monitored) at least every minute to check the system’s status by verifying:

1. API responsiveness:
   • Request:

     [platform path]/api/v1/auth-service/balance

   
   
   • If successfully connected without authorization, a 401 response should be returned.
   
   
2. Root URL accessibility (this method does not guarantee that the database is operational):
   • https://localhost:8443/ should respond with a 200 status code and the platform’s HTML page.

4. Failure Response Plan

4.1. Administrator Actions Upon Detecting an Incorrect Response:

1. Resolve network issues (if applicable).
2. Resolve hardware issues (if applicable).
3. If previous steps do not help – restore from a virtual machine snapshot, database backup, or full system backup.

4.2. Backup Recommendations

To minimize data loss, the following backup scheme is recommended:

• Daily incremental database backups;
• Weekly full database backups;
• Monthly full system backups.

Please note: When restoring from a backup, any data created after the last backup will be lost. This will primarily affect new users or resources, and event logs for that period will also be lost.

4.3. Clustered Platform

If a cluster is used, failover to a backup server occurs automatically, meaning most issues are resolved without impacting the end user. We recommend this option.

5. Post-Failure Recovery

To restore the platform to operational status, follow these steps:

1. Perform recovery according to the selected procedure.
2. Ensure all services are running and functional.
3. Test authentication on client devices.
4. Notify responsible personnel upon completion of recovery.

6. Preventing Future Failures

• Regularly check the integrity of backups.
• Perform test recoveries to verify the functionality of backup copies.
• Conduct stress tests to assess platform load capacity.
• Configure alerts for administrators about critical events.

This information is intended to minimize risks and help respond quickly in the event of issues with the Protectimus On-Premise MFA Platform.

If you have other questions, contact Protectimus customer support service.