Do you know that you can include our Agent in your Pipeline to make the verifications before deploying your product to production? In the scope tab of the ARM Platform, there is DevSecOps Agent, where you can generate new tokens or go directly to the documentation and install it.

We would love to hear about your experience with this ARM section: Has the agent been installed in your pipeline? If not yet, we warmly invite you to do so! Utilize this remarkable tool and witness its capabilities. If you have any questions, feel free to leave a comment here or send them to help@fluidattacks.com.

You can now enjoy the information on our website in Spanish. We aim to ensure that every visitor understands our offer without language barriers. Click on the following link https://fluidattacks.com/es/  and enjoy this new improvement.

Great news! You now have the option to add your credentials/secrets to your AWS environment. This will allow us to access your environment and detect any vulnerabilities in your infrastructure. Add them to the Scope -> Git Root -> Environments -> Cloud -> AWS option. 

Don't wait any longer; add your credentials/secrets now and keep your AWS environment safe from potential vulnerabilities. If you want to learn more, visit our official documentation. Stay up-to-date with all our announcements by subscribing to our News channel.

Our DevSecOps agent can break the build to force the remediation of vulnerabilities when strict mode is enabled. Still, when the strict way is disabled, the agent will only generate a warning. You can find a chart named Your commitment towards security, showing the number of builds you have deployed with strict mode enabled and how many are disabled. This can give you an idea of how committed you are to preventing vulnerable builds from reaching production.

Do you know the different types of events that can be reported on the ARM platform?  We invite you to access our official documentation, where you can learn about them and thus better understand the events that may take place in your projects. Remember that if you have any questions or feedback, please do not hesitate to contact our support team at help@fluidattacks.com. Also, we want to keep you updated on the features of our ARM platform; that is why we recommend you subscribe to our News channel so that you don’t miss any of our announcements.

Do you know the Temporal acceptance: maximum number of assignments for a single vulnerability policy? This policy helps us define how many times I can request a temporarily accepted for the same vulnerability.

If you want to know more about the Policies of our ARM Platform, we invite you to click here.  We also invite you to subscribe to our News Channel and do not miss the weekly announcements.

We work daily to improve the Security Standards we implement in Fluid Attacks. Today we want to tell you about the standard General Data Protection Regulation (GDPR); this regulation lays down rules relating to the protection of natural persons about the processing of personal data and rules relating to the free movement of personal data.

The version used in this section is GDPR - OJ L 119, 4.5.2016. Remember, you can find this and other standards we are applying in the Compliance section of our Documentation.

Do you know what the Permanent acceptance is in the Policies section? Here you can set the vulnerability type you want to be permanently accepted at the Organization level, applying it to all the groups that compose it. We invite you to enter here to learn more about this section.

Remember that if you have any questions or feedback, please do not hesitate to contact our support team at help@fluidattacks.com. Also, we want to keep you updated on the features of our ARM platform; that is why we recommend you subscribe to our News channel so that you don’t miss any of our announcements.

Every day, one of our considerations is how many vulnerabilities are open, closed, and accepted. You can find this information in the chart under the label Distribution of vulnerabilities by group. There, you can see the percentage of vulnerabilities with the defined treatment for each group. This information helps you monitor vulnerability treatments and remediation in your groups.

This chart is in the Analytics sections of your organizations and portfolios. Don’t forget to subscribe to our News channel to stay updated.

In the Policies section of our ARM platform, you will find the first policy called Temporal acceptance: Maximum number of days for assignment, which helps you to define the maximum number of days that a vulnerability can be temporarily accepted.

Thanks to defining this number of days, you can be sure that the Agent will be activated and break the build when seeing that the vulnerability does not comply with the stipulated policy. If you want to know more about the Policies section, we invite you to enter here. Subscribe to our News Channel so you don't miss our weekly announcements.