What is Security-Audit?

Monitor it before deciding. Security-Audit has not been categorized, so there is no established behavior profile to rely on. Review which pages it requests and how often, then block it if the traffic is excessive or targets content you would not share with an unknown bot. For context, 7% of the top websites we track currently have robots.txt rules for Security-Audit.

Yes. Security-Audit is expected to follow robots.txt rules, so a disallow rule is the appropriate first step. Automatic Robots.txt can add and maintain that rule, while Agent Analytics lets you verify whether Security-Audit respects it.

Unknown. Security-Audit has no established scope, so monitor what it requests. Repeated attempts to reach login or admin paths are a reason to investigate or block it.

Agent Analytics tracks Security-Audit visits in real time. You can also check your server logs for requests whose user-agent string contains "Security-Audit". Record the paths it requests and how often because no reliable behavior profile exists yet. Because Security-Audit does not publish a verification method, any client can claim its identity and a log match is only a clue.

Security-Audit's purpose has not yet been identified. Until it is categorized or its operator explains it, its behavior on your site is the best evidence of its intent.