Business Continuity Plan (BCP)
Axelerant, by its remote-only nature, is not easily affected by typical causes of business disruption, such as local failures of equipment, power supplies, telecommunications, social unrest, terrorist attacks, fire, or natural disasters.
For a business continuity plan to be effective, it needs to be triggered as soon as possible; too early or late can reduce its efficacy. Critical decision points to consider when a BCP is activated follow:
When an incident turns into a disaster, breach, or something that classifies it as a https://axelerant.atlassian.net/wiki/spaces/OA/pages/2983624719/Security+Incidents#Incident-Severity level 1.
The estimated time of resolution for a potential breach is greater than the standard estimated time for regular https://axelerant.atlassian.net/wiki/spaces/OA/pages/2983624719.
When the recovery of an incident is uncertain, decide to invoke the business continuity plan when unable to resolve the situation within the specified https://axelerant.atlassian.net/wiki/spaces/OA/pages/2983624719/Security+Incidents#Incident-Recovery-Timelines.
When the resolution of an incident with critical customers, depending on their service-level agreements, is delayed, we must trigger the BC plan.
We’ve been in business for over 10+ years and have tested our resilience and haven’t come across any incident that has been beyond our risk management abilities.
During the ordinary course of our business, we’ve managed client-specific escalations through our support portal, which has Service Level Agreements commitments. We’ve maintained zero SLA violations for the last two years. Further, any service degradation was restored within the stated SLAs by our vendors.
BCP for Remote Workers
In the case of an all-remote company like Axelerant, it is sufficient to have simple contingency plans in the form of service-level agreements with companies that host our data and services. The advantage of an all-remote workforce like Axelerant is that if there are clusters of people or systems unavailable, the rest of the company will continue to operate normally.
Data Continuity Plan
Axelerant uses all third-party SaaS platforms, logged at , and there’s no infrastructure of ours to manage. The only business risk known is service degradation without data loss.
Vendor Communication and Service Restoration Plan
All vendors’ and service providers’ support contact details are readily available and logged alongside the above subscriptions. Should a disruption of any kind, we can escalate immediately and update the time frame for service restoration.
Communication Plan and Role Assignments
All our services availability is being monitored proactively by UptimeRobot, and we manage escalations via . Any disruptions are reported transparently organization-wide via slack, email, and phone.
Further, our people operations team is a four-member which manages these subscriptions. The admin details of each subscription are available in LastPass, which is a secure way for us to share credentials without exposing them to hackers. The team members are not co-located, which enables us to de-risk and provides a point of contact for our team for any emergencies they may encounter.
We have a decentralized leadership with nine directors managing separate business areas. We have 2 CXOs who operate from different parts of the world and have equal business know-how and legal rights to act on each others’ behalf.
Business Continuity Test
After formalizing the business continuity plan, or BCP, the next important step is to test the method. Testing verifies the strategy’s effectiveness, trains plan participants on what to do in a real scenario, and identifies areas to strengthen the plan.
We review this policy at least annually or when the Axelerant Leadership team makes significant business changes.
References