Training crawlers
ISSCyberRiskCrawler is a bot operated by ISS-Corporate that collects pages used to train AI models. Used to train machine learning based models to quantify cyber risk. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"ISSCyberRiskCrawler"
Checked against
Nothing published
Live check
No operator check exists for ISSCyberRiskCrawler. This still shows what the address really is.
Reference
| User agent | ISSCyberRiskCrawlerToken only: match on the substring. |
|---|---|
| Operator | ISS-Corporate |
| Purpose | Scrapes data to train machine learning models. |
| Respects robots.txt | Ignores |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | ISSCyberRiskCrawler |
| Operator documentation | None published |
Used to train machine learning based models to quantify cyber risk.
robots.txt
ISSCyberRiskCrawler is documented as ignoring robots.txt. Enforce a block at your CDN too.
User-agent: ISSCyberRiskCrawler
Disallow: /User-agent: ISSCyberRiskCrawler
Allow: /User-agent: ISSCyberRiskCrawler
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking ISSCyberRiskCrawler keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.
Build a file for every crawlerFAQ
ISSCyberRiskCrawler is a bot operated by ISS-Corporate that collects pages used to train AI models. Used to train machine learning based models to quantify cyber risk. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Site-owner reports suggest ISSCyberRiskCrawler does not reliably follow robots.txt. Add the rule anyway, then check your logs; if requests continue, block at the edge by user agent or source address.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the ISSCyberRiskCrawler token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking ISSCyberRiskCrawler keeps your pages out of the next training run. It does not remove anything already collected, and it has no effect on how the site ranks in ordinary search.