ZeroHour

Search: “bots”

13 stories

F5 Bot Defense uses real-time risk scoring to detect fraud and abuse

F5 enhances Distributed Cloud Bot Defense with persistent device identification, real-time risk scoring, and agent-aware policies to manage AI agent traffic.

F5 announced enhancements to Distributed Cloud Bot Defense adding persistent device identification, real-time device risk scoring, risk-based workflow enforcement, and an agent-aware policy framework integrated with the F5 Application Delivery and Security Platform. The features aim to expose multi-account abuse, credential stuffing, and account takeover while allowing trusted AI agents to transact at machine speed. It targets fraud and abuse detection as agentic AI becomes a key interaction channel for sites, apps, and APIs.

Help Net Security · 1d agoTools

Say it once: Introducing Bot Preference Sync

Cloudflare launched Bot Preference Sync, which automatically syncs robots.txt files with AI bot policies covering search, agent, and training crawlers.

Cloudflare's new Bot Preference Sync feature automatically aligns a site's robots.txt with its configured AI bot policies for Search, Agent, and Training bot categories. The goal is to let site owners manage which automated and AI crawlers access their content without manually maintaining static robots.txt files.

Cloudflare Blog · 25d agoTools

Have it both ways: stay discoverable in search while disallowing AI training

Cloudflare launches Disallow AI Training setting letting sites block AI training via robots.txt while staying indexed in search; Apple, Google, and Microsoft honor it.

Cloudflare announced a 'Disallow AI Training' setting that publishes a no-training preference in robots.txt so sites can block AI training (including by mixed-use crawlers) without losing search indexing. Apple, Google, and Microsoft meet Cloudflare's new 'Accountable' designation, which requires training/summary opt-out mechanisms, URL-level training visibility, and assurance that opt-outs don't affect search rankings. Cloudflare cites that under 1% of its sites block search bots while 17% block AI training, and its Block settings now apply to mixed-use crawlers as well. Granular controls over how much content appears in AI summaries are planned for early next year.

Cloudflare Blog · 1d agoTools

Bot detection arrives in CrowdSec 1.8.0, along with two DoS fixes

CrowdSec 1.8.0 adds WAF bot detection via challenges and fingerprinting and fixes denial-of-service flaws in HTTP and Kubernetes audit datasources.

CrowdSec 1.8.0, released August 31, introduces bot detection in its WAF using client challenges and fingerprinting, plus fixes for two denial-of-service vulnerabilities in the HTTP acquisition datasource (unbounded decompressed body size, trusted Content-Length) and the Kubernetes audit webhook datasource (unbounded request body reads). The release also adds a dedicated Kubernetes datasource pulling logs directly from the apiserver, new HTTP helpers for external queries in the expression language, and performance work on the decisions stream endpoint. The challenge requires SSE4.1 and writable-executable memory, so some legitimate visitors may be blocked.

Help Net Security · 15d agoTools

Introducing More Granular Controls for AI Bot Traffic

Akamai introduced more granular controls for managing AI bot traffic within its bot management platform.

Akamai announced the introduction of more granular controls for handling AI bot traffic in its bot management offering. Detailed feature specifications were not available in the provided source text, which included only the title.

Akamai Blog · 13d agoTools

Introducing Adaptive Intelligence: Undermining the economics of every bot attack

Cloudflare launches Adaptive Intelligence, an engine that autonomously learns live-traffic meta-signals and deploys disposable rules to raise bot attack costs.

Cloudflare introduced Adaptive Intelligence, a bot-management engine that autonomously learns meta-signals from live traffic and deploys disposable detection rules. The company says static, deterministic rules historically let bot operators keep attacks cheap by using cheap proxies and rapid retooling. The new approach aims to make automated bot attacks economically unsustainable to sustain.

Cloudflare Blog · 16d agoTools

Bulk AbuseIPDB reporting using command-line tools

A blogger shows how to bulk-report distributed botnet IPs scraping a self-hosted Gitea instance to AbuseIPDB using bash, awk, and jq.

The author's self-hosted Gitea instance was scraped by distributed bots using random IPs worldwide and randomized, often nonexistent User-Agent strings, generating heavy request load for days. The write-up demonstrates filtering Traefik access logs (CLF and JSON) with grep, awk, and jq to extract offending IPs, tagging them with AbuseIPDB category 19 (Bad Web Bot), deduplicating them, and building a CSV for the Bulk Reporter tool. Reports can then be submitted through the AbuseIPDB bulk-report API, respecting the 5,000-report daily limit.

Lobsters · security · 6d agoTools1

This Key Will Self-Destruct: An Open Standard for Revocable API Keys

SecurityWeek opinion piece proposes ORKS, an open standard adding issuer prefixes, discovery files, and unauthenticated revocation endpoints to make leaked API keys quickly revocable.

The article argues that plain API keys leak frequently yet lack any standardized revocation mechanism, unlike OAuth tokens which gained RFC 7009 revocation in 2013, and that GitHub's Secret Scanning Partner Program solves this only in a proprietary, invite-only way. The author proposes ORKS (Open Revocable Key Standard), with a draft spec on GitHub, built on four parts: keys embedding their issuer domain in a fixed prefix format, a discoverable /.well-known/api-key-config JSON file, unauthenticated revocation by possession of the full key, and declared constraints such as IP allowlists, expiry, scopes, and mTLS. An optional quarantine mode inspired by Toyota's andon cord restricts a reported key to read-only and throttled operation for a default 24-hour window before automatic revocation. The piece frames AI agents as making this urgent, since agents hold many credentials, can exfiltrate them via prompt injection, and can leak secrets into logs at machine speed.

SecurityWeek · 7d agoTools1

BugBase Pentest Copilot Enterprise automates black-box pentesting

BugBase launched Pentest Copilot Enterprise, an autonomous AI black-box pentesting platform using parallel agents to attack 100 vulnerability classes with validated PoCs.

BugBase announced Pentest Copilot Enterprise, which performs black-box red teaming without source-code access while maintaining authenticated context. Parallel specialized agents map pages, APIs, accounts and business functions, then execute iterative attacks across 100 vulnerability types including authentication, injection and business-logic flaws. The tool uses real Chromium browsers to preserve cookies, tokens, CSRF state and multiple identities, and navigates WAFs, bot detection, CAPTCHA and T-OTP. BugBase claims full scope coverage on OWASP Juice Shop, Broken Crystals and GOAD, NHA, and DRACARYS Active Directory labs.

Help Net Security · 12d agoTools