What happened

• We are currently working on standardizing our infrastructure through nix.
• At 14:33 (COT), our team deployed a change that made use of docker experimental syntax. We expected that it would only affect the base infrastructure, but, due to the way docker works internally, caches for Integrates containers were also lost.
• At the same time, one of our sub-dependencies was updated and broke our source code compatibility.

What we’ve done

• After an intensive debug process, our team reproduced the issue at 10:33 (COT) on 2020/10/10.
• We implemented a temporary solution and restored the service at 10:40 (COT) on 2020/10/10.
• We committed a definitive fix at 11:00 (COT).
• We committed a complementary solution at 11:32 (COT).

What the impact was

• Users were unable to login to Integrates or to use the API from 2020/10/09 14:33 until 2020/10/10 10:40.

What we are doing to help

• Continue standardizing our infrastructure: https://gitlab.com/fluidattacks/product/-/issues/3504
• Freezing all deps and sub-dependencies: https://gitlab.com/fluidattacks/product/-/issues/3522
• Standardizing async helpers: https://gitlab.com/fluidattacks/product/-/issues/3521

What happened

• We are currently working on a huge backend migration on Integrates. A substantial part of this change concerns the login process and Integrates’s URLs.
• After introducing this change, we noticed that we had some problems related to the Integrates deployment process. We are currently deploying a second version of Integrates for testing purposes, which is the one that is failing, oriented to support the mentioned backend migration.

What we’ve done

• We noticed the issue today, Oct 9, at 12:20 AM, and committed the fix at 12:40 AM.

What the impact was

• Users were unable to login to Integrates for 20 minutes.

What we are doing to help

• We are improving our production backend deployments—open issue.

On our way to improve ARM, the time has come for the well-known portfolios.

We updated all graphics and indicators according to the new analytics 'look and feel.'

Remember that you can subscribe and receive an email with these reports.

What happened

From Monday afternoon to Tuesday, we experienced problems with Integrates’s authentication process due to an overload in the number of operations on one of the databases, which was the result of the integration between Integrates and Asserts we are currently implementing.

What we’ve done

When the cause of the problem was found, we restarted the database instance and, subsequently, modified the server’s specifications to improve its performance and respond to these new requirements

What’s the impact

There were approximately 200 failed login attempts in the application between Monday, September 30th at 5:27 p.m. and Tuesday, October 1st at 1:37 p.m. that resulted in an Error 500 response.

What we are doing to help

We improved the instance to support a greater number of connections, and we are permanently monitoring the database in case more resources are required to continue responding to all requests properly.

Since we have the new analytics dashboard, we included some graphics and indicators. Now the time is for organizations' data.

In your organization's dashboard, you will find interesting data about all your groups, such as how many findings or vulnerabilities your entire organization has.

All these features are the product of a team effort. You can be part of it and create new elements by joining the Fluid Attacks Community or sending your comments to help@fluidattacks.com.

What happened

• Last Friday (September 20th) there was an incident in which emails about accepted findings were massively sent.
• We are currently finishing the implementation of the functionality which allows setting a time limit for the acceptation of findings on the platform.
• The final step of this functionality is to assign a maximum time of three months to all existing findings that have already been accepted. In the process of performing the latter, due to a programming error, the acceptation emails were sent again and multiple times.
• The programming mistake that was made allowed the script that updates the acceptation dates of findings to be executed repeatedly and without notice from a development workstation.

What we’ve done

• As of today (September 23rd), the programming errors have been solved and the emails will not be sent again in this process.
• To avoid future occurrences of this type, we have restricted the credentials that we used to send all the emails, so now a double check is needed to send any of them.

What’s the impact

• Approximately 100,000 emails were sent to customers. The users that were affected the most were those who had several projects with assumed findings, receiving up to 1100 emails.
• No finding that had not previously been accepted was modified, nor were their justification and treatment manager modified.

What we are doing to help
With this announcement, customers are being notified that this does not represent a security threat and was only an internal error.

What happened

• Due to a firewall misconfiguration, users were not able to login.

What we’ve done

• We reverted the firewall change that caused the issue.

What’s the impact

• Users were unable to login from 18:43 to 19:11.

What we are doing to help

• We are working on preparing the application for the new set of firewall rules, including the ones that caused the issue.

From October 1st, 2020, the endpoint for Integrates API will change to integrates.fluidattacks.com/api.

You will only be able to use the Integrates API from the new endpoint.

We strongly recommend you to update your scripts ASAP to avoid unexpected behaviors.

All these features are the product of a team effort. You can be part of it and contribute to the creation of new elements by joining the Fluid Attacks Community or sending your comments to help@fluidattacks.com.

From October 1st, 2020, the Integrates domain will change to:
integrates.fluidattacks.com.

You will only be able to access our system on the new domain.

All these features are the product of a team effort. You can be part of it and contribute to the creation of new elements by joining the Fluid Attacks Community or sending your comments to help@fluidattacks.com.