<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>misconfiguration</title>
    <link rel="self" type="application/atom+xml" href="https://links.biapy.com/guest/tags/2672/feed"/>
    <updated>2026-08-24T04:48:46+00:00</updated>
    <id>https://links.biapy.com/guest/tags/2672/feed</id>
            <entry>
            <id>https://links.biapy.com/links/11576</id>
            <title type="text"><![CDATA[aura-inspector]]></title>
            <link rel="alternate" href="https://github.com/google/aura-inspector" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11576"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[aura-inspector is a Swiss Army knife of Salesforce Experience Cloud testing. It facilitates in discovering misconfigured Salesforce Experience Cloud applications as well as automates much of the testing process. Some of it&amp;#039;s functionality includes:

Related contents:

- [Erreur 403 | \#60](https://newsletter.erreur403.fr/p/erreur-403-60).
- [ShinyHunters claims more high-profile victims in latest Salesforce customers data heist @ The Register](https://www.theregister.com/2026/03/09/shinyhunters_claims_more_highprofile_victims/).]]>
            </summary>
            <updated>2026-03-12T10:49:18+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/11573</id>
            <title type="text"><![CDATA[Gixy-Next]]></title>
            <link rel="alternate" href="https://gixy.io/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/11573"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[NGINX Configuration Security &amp;amp; Hardening Scanner.

Gixy-Next (Gixy) is an open-source NGINX configuration security scanner and hardening tool that statically analyzes your nginx.conf to detect security misconfigurations, hardening gaps, and common performance pitfalls before they reach production. It is an actively maintained fork of Yandex&amp;#039;s Gixy. Gixy-Next&amp;#039;s source code is available on GitHub.

- [Gixy-Next @ GitHub](https://github.com/MegaManSec/Gixy-Next).

Related contents:

- [Erreur 403 | \#60](https://newsletter.erreur403.fr/p/erreur-403-60).]]>
            </summary>
            <updated>2026-01-23T07:23:55+00:00</updated>
        </entry>
            <entry>
            <id>https://links.biapy.com/links/6404</id>
            <title type="text"><![CDATA[Trivy]]></title>
            <link rel="alternate" href="https://trivy.dev/" />
            <link rel="via" type="application/atom+xml" href="https://links.biapy.com/links/6404"/>
            <author>
                <name><![CDATA[Biapy]]></name>
            </author>
            <summary type="text">
                <![CDATA[Trivy (pronunciation) is a comprehensive and versatile security scanner. Trivy has scanners that look for security issues, and targets where it can find those issues.

Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more.

- [Trivy @ GitHub](https://github.com/aquasecurity/trivy).
- [Trivy Documentation](https://aquasecurity.github.io/trivy/).
- [Integrer la sécurité dés le départ avec Trivy @ Culture et Outils DevSecOps :fr:](https://blog.stephane-robert.info/docs/securiser-projets-trivy/).
- [Trivy Is Noise by Default, Here’s the Seven-Rule Filter That Catches Real Risk @ DevOpsDynamo&amp;#039;s Medium](https://medium.com/@DynamoDevOps/trivy-is-noise-by-default-heres-the-seven-rule-filter-that-catches-real-risk-05c4c3249c26).
- [Blueprinting Security in CI/CD: Building Trust Through Open Source @ CD Foundation](https://cd.foundation/blog/2026/02/06/blueprinting-security/).
- [20 Days Later: Trivy Compromise, Act II @ Boost Security Labs](https://labs.boostsecurity.io/articles/20-days-later-trivy-compromise-act-ii/).
- [Trivy supply chain compromise: What Docker Hub users should know @ Docker blog](https://www.docker.com/blog/trivy-supply-chain-compromise-what-docker-hub-users-should-know/).
- [Trivy compromis une seconde fois : la release v0.69.4 était empoisonnée @ DevSecOps :fr:](https://blog.stephane-robert.info/post/trivy-actii/).
- [When Security Scans Break the Brain: Solving Trivy’s etcd Exhaustion Problem @ aqua](https://www.aquasec.com/blog/when-security-scans-break-the-brain-solving-trivys-etcd-exhaustion-problem/).]]>
            </summary>
            <updated>2026-07-06T11:39:55+00:00</updated>
        </entry>
    </feed>
