Business Continuity Management

VulDB is proud to provide a very robust and highly reliable service for more than 25 years. This is possible due to a professional Business Continuity Management (BCM).

Basic Principles

We provide the highest Tier 7 Preparedness according to the IBM eight tier model which is defined as:

Tier 7 - Highly automated, business-integrated solution: Tier 7 solutions include all the major components being used for a Tier 6 solution with the additional integration of automation. This allows a Tier 7 solution to ensure consistency of data above that of which is granted by Tier 6 solutions. Additionally, recovery of the applications is automated, allowing for restoration of systems and applications much faster and more reliably than would be possible through manual Disaster Recovery procedures.
We provide high-availability with georedundancy for our core services. Data centers are ISO 27001 and PCI DSS certified and the service is fully GDPR and CCPA compliant.

A full backup of all data happens once per day and is stored in two separate locations. A full restore is tested once per year and possible in under 120 minutes.

IDThreatResilienceGuidelinesPreparedness
1Epidemic/PandemicHealth requirements (e.g. testing, social distancing, hand sanitizing, masks, vaccination, paid isolation during illness), remote working encouraged, adequate teams, staff rotation, cooperation with civil defence authorities (e.g. Federal Civil Defence Office), proven during COVID-19ISO 27001
High
2FireFire suppression systems in data centers, georedundant data centers, data synced in real-time, off-site backups, trained employees, recurring audits by authoritiesISO 27001
High
3FloodLow risk locations, georedundant data centers, some of them in 1st floor or above, data synced in real-time, cooperation with civil defence authorities (e.g. police, Federal Civil Defence Office)ISO 27001
High
4EarthquakeLow risk locations, georedundant data centers, data synced in real-time, cooperation with civil defence authorities (e.g. police, Federal Civil Defence Office)ISO 27001
High
5Hurricane/StormLow risk locations, georedundant data centers, data synced in real-time, cooperation with civil defence authorities (e.g. police, Federal Civil Defence Office)ISO 27001
High
6Power OutageInterruption-free power supply, emergency power unit, georedundant data centers, data synced in real-time, minimized dependency on international energy suppliersISO 27001
High
7Water OutageLow importance, georedundant data centers, data synced in real-time, remote working possibleISO 27001
High
8IT OutageGeoredundant data centers, data synced in real-time, off-site backups, high-availability, emergency caches available, recurring security testing, public bug bounty programISO 27001, RFC 9116
High
9Telecomms OutageRedundant internet access, georedundant data centersISO 27001
High
10MisconfigurationConfiguration guidelines, dev and test environments, reviews required before production, immediate fallback possible, recurring security testing, public bug bounty programISO 27001, PCI DSS, RFC 9116
High
11Data CorruptionBest practice security measures, georedundant data centers, data synced in real-time, off-site backups, data validation, cryptographic signatures, commit history, monitoring, alerting, recurring security testing, public bug bounty programISO 27001, RFC 9116
High
12Cyber AttackBest practice security measures, data classification, privacy policy, secure development lifecycle, hardening, network access control, firewalling, malware detection, IDS, IPS, DLP, logging, monitoring, alerting, off-site backups, high-availability, recurring security testing, public bug bounty programISO 27001, PCI DSS, RFC 9116
High
13SabotageScreening of employees, no subcontractors allowed for critical tasks, best practice security measures, data classification, data integrity validation, commit history, monitoring, alerting, off-site backups, high-availabilityISO 27001
High
14TheftPhysical access limitation, video surveillance, logging, monitoring, alerting, data classification, privacy policy, encryptionISO 27001, PCI DSS
High
15Terrorism/PiracyLow risk locations, best practice security measures, georedundant data centers, data synced in real-time, off-site backupsISO 27001
High
16War/Civil DisorderLocation in highly stable countries (e.g. Switzerland), geopolitical monitoring to anticipate problems, no dependencies on location, georedundant data centersISO 27001
High
17Single Point DependencyPrevented at all cost, dependencies minimized, redundancy and alternatives as requirementISO 27001
High
18Random Failure of Mission-Critical SystemsHigh availability, hot-standby, georedundant data centers, data synced in real-time, off-site backupsISO 27001
High
19Supplier FailureReduced dependencies (e.g. internal development of core services), standardized services, alternative suppliers available immediatelyISO 27001, PCI DSS
High

Monitoring and Alerting

Availability of network interfaces, services, and data integrity is monitored in real-time by two different monitoring frameworks. Data integrity is monitored by two other systems.

Disruptions and other problems are reported immediately to the responsible team via email, push notification, or text message. These alerts include details about the affected component and the suspected root cause. They do also contain the recommended steps to reproduce and mitigate the problem.

Team leads are instructed and trained to maintain the expected level of availability. High-availability based on redundancy and hot-standby makes it very easy to act quickly without knowing the root cause of a problem immediately. Analysis happens after reinstating service availability.

Minimized Dependencies

Our processes are highly simplified and independent from each other to guarantee the maximum of flexibility and efficiency.

Technology dependency is reduced to an absolute minimum. We use well-known components and products for the service. Core components are developed inhouse to aim for ideal performance, reliability, and flexibility.

We have also tested alternative products and solutions (e.g. other web server implementations and database engines) to switch to them quickly if this becomes necessary (e.g. because a product is end-of-life all of a sudden).

Internal systems are not required to provide our customer service. We use internal systems for development, testing, sales, accounting, etc. Their availability does not and cannot influence the customer experience of the service as they are deployed on a separate environment without direct connectivity nor dependency on the productive server environment.

Our suppliers provide standard services (e.g. web hosting and payment processing). There are many similar competing suppliers which would be available immediately if the situation requires such a change. All our robust interfaces are prepared for redundant implementations and quick switching.

Extended Analysis

We have different teams which are responsible to establish and maintain their products and guarantee the expected level of availability. The teams are well staffed, which guarantees steady reliability in cases of fluctuation, illness or other events with negative impact.

  • Hardware team
  • Network team
  • Operating system team
  • Application team
  • Database team
  • Data team
As soon as the service availability is guaranteed again, it is required to identify the cause of the problem. The result of this analysis is reported to BCM management which incorporates lessons learned in future alerting and mitigation handling.

We do regular testing of availability and BCM mechanisms to verify the expected goals.

Human Resources

We have different teams which are responsible to handle their processes. These teams consist of a team lead and at least one additional co-team lead. Core tasks are handled by a sub-board consisting of at least three people. All task assignments are are shared between two or more people to guarantee coverage during events like days off, illness, or others.

Recovery Time Objective

The Recovery Time Objective (RTO) is set to 72 hours. Commercial customers might define other targets aligned with their expected Service Level Agreement (SLA).

Interested in the pricing of exploits?

See the underground prices here!