Know the differences between continuous hacking and one-shot hacking offered by
Fluid Attacks. To this end we present the following table:
Table 1. Comparison between Continuous and One-Shot Hacking services.
Aspects |
Continuous Hacking |
One-Shot Hacking |
|
Multiple 1. |
Only 1 1. |
|
 Yes. 2
|
 No. 2
|
|
12-36 months 3. |
1-4 months 3. |
|
A minimum of 5 hackers test your system. |
 A minimum of 2 hackers test your system.
|
|
Unlimited within the contract period.
All information deliveries are made via
our Attack Surface Manager (ASM)
4. |
Limited to two within the contract period:
|
|
Early
|
Late
|
|
Continuous alerting system via email
to the project stakeholders about the current state of the project
5. |
Alerting system via email to the project stakeholders
when an anomaly is reported. |
|
Up-to-date information about your system’s security. |
Information about your system’s security
at only one particular point in time. |
|
100% when:
-
We start simultaneously with development.
-
We attack all versions of the existing code
up to the subscription starting point to catch up,
if necessary, with the development team.
-
Hacking does not stop, even without new developments in the project.
|
Agreed upon by both the customer and Fluid Attacks
before testing begins
6.
|
|
Environments:
|
Frozen environments and test windows are required. |
|
Environments are not infected with cyberweapons. |
Work stations and critical servers
are infected with cyberweapons. |
|
Up to 100% of reported vulnerabilities can,
potentially, be remediated. |
Up to 80% of reported vulnerabilities can,
potentially, be remediated. |
|
Remote. |
Remote or on premises. |
|
2 - 3 weeks. |
3 - 4 months. |
|
Monthly payment. |
1 or 2 payments.
|
Want further information about our services?
Do not hesitate to
contact us.
