Continuous Hacking is a security testing service
that allows the hacking process to begin at an early stage
in the software development cycle.
Its purpose is to guarantee
100% testing coverage of the application.
Continuous Hacking: . Minimizes the cost of remediation (repair) of a vulnerable security risk while the software is in development rather than when it is in production.
Reduces application certification time to zero because the hacking is done during development.
Provides clear and detailed information about vulnerable security risks
and facilitates a coordinated effort between external project personnel
Fluid Attacks experts) identifying security risks,
and internal project personnel (client company)
fixing security issues without delays.
Along our career trajectory we have been working with companies from different sectors, such as financial, transportation, industrial, consumer, communications, technology and utilities.
We ensure to constantly research and keep updated
with the new techniques and changes related to cybersecurity and
Through blog entries
we keep our team updated with the state of art.
The necessary inputs and requirements are:
Phase 1: Access to the integration branch of the repository for the not-yet-deployed application’s source code. Ethical Hacking focuses on the source code.
Phase 2: When the project has a deployed application (Integration Environment), the hacking coverage expands to include application security testing.
Phase 3: This phase applies only if the infrastructure supporting the application is defined as code and kept in the integration branch of the repository referred to in Phase 1. This phase includes infrastructure hacking.
Git and a monitored environment in the branch are required,
through automated Linux.
The following environments are not supported:
Access through a
VPN that only runs on
Windows that requires manual interaction such as an
VPN Site to Site.
Continuous Hacking includes source code analysis, application hacking (see question 5), and infrastructure hacking (see question 5).
A vulnerability is anything that represents a security risk (Integrity, Availability, Confidentiality, Non-repudiation) to the application.
An active author is a user with access to the
who makes changes to the stored code in the repository during
the analyzed month.
Automated tools, by themselves,
are not capable of extracting sensitive business information,
such as client or employee information.
In our Continuous Hacking service, we use a series of tools
which are acquired and developed by us at
as well as a detailed review process performed by our expert technical staff.
We go the extra mile because automated tools present the following problems:
Vulnerability leakages (detection of a minimal percentage of existing security risk vulnerabilities).
Detected vulnerabilities are primarily false positives.
Incapability of combining individual vulnerabilities in order to reveal additional vulnerabilities which may be an even greater security risk than the individual vulnerabilities alone.
Continuous Hacking is first performed on the source code.
This allows for hacking and development to occur simultaneously,
which in turn minimizes the dependency on functional environments,
as well as the need for coordination between hackers and developers.
The decisions regarding which findings are prioritized for each sprint
rest solely with the client.
Unless we are dealing with a company with daily
(Continuous Integration/Continuous Deployment),
not all sprints generate code eligible for release and deployment,
which improves the remediation (repair) time for detected vulnerabilities.
Standard Continuous Hacking
95% of all business applications being developed,
as the subscription is based on the number
of active developers in the project and this defines the amount of resources
assigned to the project.
Based on our historical data,
and thanks to our recruitment and training capabilities,
as well as our ability to innovate internal processes,
we are fully capable of taking on
10 new applications each month.
To provide a proposal, we need to determine what the target of evaluation (scope) will be. So, we require the following information:
One-shot hacking (by project):
How many ports are included in the scope?
How many inputs of applications are included in the scope?
LoC are included in the scope?
We recommend running
in order to facilitate quantification.
Note: It would be desirable to obtain the access credentials (standard user, not privileges) to the applications in cases where this will be included.
Continuous hacking (
Under this model, we need to know how many active authors
will be involved in the project.
Regarding the health check estimation, the same considerations apply as for one-shot hacking, so the client should provide the above-mentioned information as well.
Yes. The service cost varies depending on the number of active authors identified in the project each month.
Continuous Hacking needs access to the source code because it is based on continuous attacks on the latest version available.
Continuous Hacking begins immediately after receiving the purchase order.
0 begins the test setup and is the start of the monthly payment.
A project leader is assigned who is responsible
for managing the connection of environments, profiling, user creation,
allocation of privileges, and all the necessary inputs
to begin the review without setbacks.
No. Due to the operational model that supports Continuous Hacking, it can only be done remotely.
Yes. All applications covered by the contract for Continuous Hacking are assigned to a specific project leader who is available to attend all necessary meetings. We simply require sufficient notice of an impending meeting in order to schedule availability.
A project’s progress and current state is determined using the following metrics: . Source code coverage indicator. . Percentage of remediated (repaired) security risk vulnerabilities.
Continuous Hacking is contracted for a minimum of
and is renewed automatically at the end of the
12-month time period.
Continuous Hacking ends when we receive a written request
through previously defined channels to terminate the contract.
You can cancel your contract at any time after the fourth month. Cancellation can be requested through any communication channel previously defined in the contract.
No. Even if
100% of coverage is reached,
we continue checking already attacked source code to identify
any possible false negatives,
including components developed by third parties in our hacking process.
Fluid Attacks uses CVSS
(Common Vulnerability Scoring System),
a “standardized framework used to rate
the severity of security vulnerabilities in software.”
It gives us a quantitative measure ranging from
0 being the lowest level of risk and
10 the highest
and most critical level of risk,
based on the qualitative characteristics of a vulnerability.
Continuous Hacking generates and delivers,
a technical report available in
Fluid Attacks reports a vulnerability,
the main objective for developers is to eliminate it.
Through Integrates, a client company’s developers can access
first-hand detailed information regarding a vulnerability
in order to plan and execute corrective measures
to remove it from the application.
For Continuous Hacking, communication takes place
between developers and hackers on a day-to-day basis via Integrates.
In One-shot Hacking, communication is handled
through the project manager (
PM) as a single point of contact (
Through Integrates, any user with access to the project can request verification of a remediated vulnerability. A request for verification that a remediated vulnerability no longer poses a risk must be accompanied by notification from you that the planned remediation has been executed. We then perform a closing verification to confirm the effectiveness of the remediation. Results of the closing verification are then forwarded to the project team by email.
Continuous Hacking offers unlimited closing verifications.
One of Continuous Hacking’s objectives is to maintain clear and effortless communication between all project members. This is accomplished when you notify us because the message goes through Integrates and by doing so, the entire project team is notified.
Within Integrates there is a comment section. A client company can post its reasons for believing a vulnerability finding is not valid. Our experts and all other project members can then interface and discuss the relative merits of the vulnerability finding as well as the validity of it as a security risk, and a final determination can be made.
No. However, this decision is made entirely by the client, not by us, and the client assumes all responsibility for possible negative impacts of non-remediation. In Integrates, under the treatment option, a client company indicates whether it will remediate or assume responsibility for an identified vulnerability.
No. Reports and Integrates include information regarding all vulnerabilities, along with whether vulnerabilities were remediated or not. Your report and Integrates will include all the information with nothing excluded.
Yes, with one condition.
The code must be stored in the same branch in each repository.
For example: If it is agreed that all attacks
will be performed on the
then this same branch must be present in all of the repositories
included for Continuous Hacking.
Yes, it is still possible to use Continuous Hacking. There are two possible options available:
A Health Check can be performed testing all existing code. Then, Continuous Hacking is executed as usual within the defined scope (see question 11). This option is better suited for applications under development.
Start with the standard limits (see question 10),
increasing the coverage on a monthly basis until
100% is reached.
This option is better suited for applications no longer in development.
We recommend that application development
and the hacking process begin simultaneously.
However, this is not always possible.
To catch up with developers,
we perform a
Health Check (additional fees apply).
This means all versions of the existing code
are attacked up to the contracted starting point
in addition to the monthly test limit.
This allows us to catch up with the development team
within the first
3 contract months.
Then, we continue hacking simultaneously with the development team
as development continues.
This is a risky choice.
Not performing a Health Check means there will be code
that is never going to be tested and, therefore,
it’s not possible to know what vulnerabilities may exist in it;
those vulnerabilities are not going to be identified.
We guarantee that
100% of the code change
is going to be tested, but what cannot be reached, cannot be tested.
Continuous Hacking is based on using
Git for version control.
Git is necessary for Continuous Hacking.
Information is only kept for the duration of the Continuous Hacking contract.
Once the contract has ended, information is kept for
7 business days
and then deleted from all our information systems.
Integrates uses an automated erasing process,
removing all the project information from our systems
and generating a
Proof of Delivery signed via
No. Continuous Hacking is independent of the client’s development methodology. Continuous Hacking test results become a planning tool in future development cycles. They do not prevent the continuation of development.
Fluid Attacks can schedule periodic presentations via teleconferencing.
To set up a teleconference presentation, you will need to provide us
with the emails of attendees and
3 optional time periods
1-hour duration for the teleconference.
We will then notify you of the best time for the teleconference
based on your availability and ours,
and send emails to your list of attendees
inviting them to participate.
No. The client can use whatever repository they deem appropriate. We only require access to the integration branch and its respective environment.
Our designated team of hackers.
Yes, you can access the
Please refer to our certifications page for further information.
No. Reviewing your code in no way compromises your proprietary rights to that code.
Yes. Asserts is
Fluid Attacks' automated engine,
checking remediation of previously confirmed vulnerabilities.
Asserts operates in the
JOB of continuous integration.
It can break the build sent by the programmer in the event
of a breach of security requirements.
We have recently released
source code to our public repository.
We have improved the Continuous Hacking model
to now include infrastructure within the Target of Evaluation (
This includes the application’s ports, inputs,
infrastructure, and of course the application itself.
It is up to you, however, we recommend the use of
for application tests and
git) for source code analysis.
The platform, Integrates, runs in the cloud.
No. We use federated authentication.
are the entities which validate your user access credentials.
Yes, it is, and we recommend you do so.
Using double authentication will increase
the security level of your credentials.
This will help prevent unauthorized users
from accessing and compromising your information.
This feature is enabled through
The goal is
Therefore, there will be results
regarding system vulnerabilities continuously throughout the contract period.
We take into account all pushes to the tested branch,
which are monitored using automated scripts (robots)
that extract and analyze the changes made to the source code every night.
Fluid Attackstest every time I make a push in the subscription branch?
During the execution of a project, the following scenarios can occur:
Application in development without overdue code (
The robot detects the change and generates the updated control files.
This means that no specific file or commit is audited,
but rather the change analysis performed by the robot is incorporated
when the hackers attack the application,
thus allowing them to take into account the changes made.
Application in production without overdue code (100% coverage): Even when there are no changes, the application is attacked. Internally, we have processes that help us identify why we haven’t found vulnerabilities in the application in 7, 14 and 21 days. These processes include such things as hacker rotations or increasing the number of hackers assigned to the project in order to find undiscovered vulnerabilities.
Application in development with overdue code (
Same as the first scenario, but attacks are only related
to the change that was made.
The attack surface that existed before the subscription point is not attacked.
Application in production with overdue code (
Same as the second scenario, but if in a specified month there is no new code,
it is hacked only to the extent of the changes
one active author in
one previous month.
Once the setup has been completed, and everything is ready for the service to begin, the security tests start. The steps are as follows:
Approval request (purchase order confirmed).
Project leader assignment.
The project leader schedules the start meeting (teleconference).
Service condition validation.
Supplies request (access to environments and code).
The project leader receives supplies, and programs the setup of the verification and access robots.
The project leader creates an admin user in Integrates for the client.
The admin user invites all project stakeholders including the developers.
(They must have
Google Apps or
Vulnerabilities are reported in Integrates.
Project stakeholders access vulnerabilities and start remediation.
If any questions or problems arise, they can be addressed through the comments or chat available in Integrates.
When the client has remediated the reported vulnerabilities, they may request validation of their repairs through Integrates.
Our hacker performs the closure verification and updates the report.
7 are repeated until the subscription ends.
Asserts runs on any continuous integration platform
Docker engine 18.03.1)
and has access to the internet.
Yes, it is available on the Asserts page.
According to the active authors model, it is possible to create a large cell with all the developers or to divide it into applications according to the client’s needs. When managing only one cell, it is important to consider the following: * All users in the project can see all the vulnerabilities of the application inside the same cell. * When the same vulnerability appears in several applications, the only way to identify/locate each one in each individual application is by checking the vulnerability report under the heading "location". There, it will specify where each vulnerability can be found.
Yes, it is possible under the condition that the new environment be the same branch environment where the source code is reviewed, thus allowing us to test the same version of the change both statically and dynamically.
It is possible to cause an accidental
DoS during the hacking service.
We recommend including only the staging phase in the scope.
However, many clients decide to also include
the production stage in the tests.
It is unusual for us to take down environments
because when we foresee a possible breakpoint,
we ask the client for a special environment
within which to carry out the test.
The service includes the environment of the reviewed code (see question 52). It is possible to include different environments for an additional fee.
All questions made through the vulnerabilities comment system,
4 business hours
SLA. M - F
12 noon and
UTC-5 Colombia = same as Eastern Standard Time
SLA is not contractually defined, it is our value promise.
1M USD coverage.