ISSCyberRiskCrawler
SafeUser-agent: ISSCyberRiskCrawler
Category: Scrapers
SEO impact if blocked: 2/10
ISS
1 crawler operated by ISS
Who ISS is, for site owners
ISS operates 1 crawler in our directory, filed under Scrapers. Its crawl behaviour is rated safe.
Blocking ISS carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for ISS: Generally safe to allow; provides legitimate crawling value.
ISS at a glance
| Operator | ISS |
|---|---|
| Crawler in directory | 1 |
| Categories | Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
Crawler operated by ISS
What ISS's crawlers are for
ISS runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
ISSCyberRiskCrawler
The highest-priority token is Tier 6. That makes ISS a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat ISS
How often site owners write rules for ISS's tokens, from our own robots.txt study of the Tranco top 10,000:
| Token | Files naming it | Files blocking it |
|---|---|---|
ISSCyberRiskCrawler | 107 (1.9%) | Not measured |
A ISS token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.
All counts come from 5,583 valid files fetched October 20, 2026.
Writing one policy for ISS
A robots.txt file cannot say "ISS"; it can only name ISS's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything ISS fetches through it
User-agent: ISSCyberRiskCrawler
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the AI search visibility check after any change to see the result for each ISS token, including firewall refusals.
Test yourself: does User-agent: ISS block all of ISS's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token ISSCyberRiskCrawler.
Test yourself: if you block one ISS token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each ISS crawler, explained
A one-paragraph brief for every ISS token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- ISSCyberRiskCrawler (
ISSCyberRiskCrawler, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated safe. ISSCyberRiskCrawler's operator does not clearly document how it treats robots.txt. Write the ISSCyberRiskCrawler rule anyway, then confirm in your logs that its requests stop. 1.9% of top-site robots.txt files name it.
Common mistakes with ISS's crawlers
The errors we see most often with ISS's crawlers in the files and firewalls we test:
- Treating ISS's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when ISS's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking ISS's crawlers by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check ISS's crawlers from outside after every change.
What our own data shows about ISS
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from ISS's marketing. ISS has one token in our database, so the whole picture fits in one place.
ISSCyberRiskCrawler in our records
We first recorded ISSCyberRiskCrawler on March 17, 2026. We could not find a page where ISS names it, so treat the token as reported rather than documented. ISSCyberRiskCrawler is outside our tracked token set, but 107 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.
Among the 39 data scrapers in our database, ISSCyberRiskCrawler sits 22th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 29 of the 39 share its safe rating. Other operators with a crawler that harvests pages for a dataset or data product: FirecrawlAgent (Firecrawl, Tier 2), iaskspider (iAsk, Tier 2), NovaAct (Amazon, Tier 2), CloudflareBrowserRenderingCrawler (Cloudflare, Tier 3), Amazon Kendra (Amazon, Tier 6). A policy for ISSCyberRiskCrawler is usually a policy for these too.
A decision record for ISSCyberRiskCrawler
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the ISSCyberRiskCrawler entry reads:
- Operator and job: ISS; it harvests pages for a dataset or data product.
- Priority and behaviour: Tier 6, rated safe, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: ISSCyberRiskCrawler's operator does not clearly document how it treats robots.txt. Write the ISSCyberRiskCrawler rule anyway, then confirm in your logs that its requests stop.
User-agent: ISSCyberRiskCrawler
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the ISSCyberRiskCrawler entry once a quarter, or when ISS publishes a new token next to it.
Checking ISSCyberRiskCrawler on your own site
Because ISS runs only ISSCyberRiskCrawler in our records, one check covers the whole operator. Search your access logs for the string ISSCyberRiskCrawler over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. ISS publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 6 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat ISS's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for ISS's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch ISS's crawlers too.
More questions about ISS
- Will blocking ISS affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of ISS's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for ISS?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow ISS on some sections and block it on others?
- Yes. Inside the group for
ISSCyberRiskCrawler, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking ISS delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether ISS offers a removal or opt-out process.
- Is a firewall block better than robots.txt for ISS?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute ISS review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI bot checker to see the outcome from outside, including any firewall layer.
How to block or allow ISS in robots.txt
This rule covers the single crawler ISS operates. Add it to the robots.txt file at the root of your domain.
Block ISS completely
User-agent: ISSCyberRiskCrawler
Disallow: /
Allow ISS explicitly
User-agent: ISSCyberRiskCrawler
Allow: /
These ISS rules ask; they do not enforce. If a ISS token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about ISS
What crawler does ISS run?
ISS operates 1 crawler in our directory: ISSCyberRiskCrawler (user-agent ISSCyberRiskCrawler).
Should I block ISS?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block ISS in robots.txt?
Add the following to robots.txt at your domain root: User-agent: ISSCyberRiskCrawler then Disallow: /.
Does blocking ISS hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking ISS does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.