Securitylab•July 27, 2026•🇷🇺Translated from Russian

Optimizing Cybersecurity Content for LLMs: How Sites Can Enter Generative AI Answers

Search increasingly surfaces ready-made answers ahead of link lists. Services such as ChatGPT, Gemini, Perplexity, Copilot and Google AI Overviews locate source material, extract suitable fragments and assemble coherent text. Users may obtain core information without ever visiting the original site.

For site owners the nature of competition itself changes. A high position in conventional results remains valuable yet insufficient. Content must enter the index, pass selection by retrieval components, supply the required fact, receive a citation and retain meaning after paraphrasing. The final requirement is especially critical in cybersecurity, medicine, finance and law, where a distorted product description, incorrect dosage or outdated regulation can lead to harmful decisions.

GEO, AEO and LLMO without marketing fog

Optimisation for generative answers is labelled GEO, AEO or LLMO. Google treats the work as an extension of ordinary SEO. Its official guidance states that AI Overviews and AI Mode rely on the existing search index, core quality systems and familiar page requirements. GEO therefore supplements, rather than replaces, technical SEO, editorial standards and source reputation.

It is useful to view GEO as an additional measurement layer. Conventional SEO answers whether a user found the page. SEO for generative systems adds further questions: did the system locate the needed fragment, use the information, display a link, name the source correctly and preserve accuracy during summarisation.

How material reaches an answer

Different services follow different paths. Google uses its own index and may decompose a query into several related searches. ChatGPT decides whether web search is required and then consults retrieved sources. Bing links its index to the generative component of Copilot.

In simplified form the journey comprises several stages: the crawler receives the page, the search system indexes the material, the retrieval component selects documents, the system extracts fragments, the model generates the answer and the interface decides which links to show. Failure at any stage nullifies the author’s effort. A well-written paragraph is useless if a firewall blocks the crawler.

Writing material that resists distortion

An article should deliver its factual core immediately. The reader must quickly grasp the subject, the parties involved, the consequences and the required actions. Each important claim should stand alone. The sentence “developers have already closed the dangerous hole” requires restored context. The formulation “vulnerability CVE-2026-12345 permits unauthenticated code execution; the fix is included in version 8.4.2” supplies object, condition, consequence and resolution.

Concrete details outperform vague assessments. Product names, versions, dates, figures, researcher names and primary documents reduce room for speculation. Statistics, quotations and references have produced visibility gains of up to 40 percent in controlled experiments, although later reviews found no universal technique that reliably improves organic visibility across platforms over long periods.

Original data create a reason to cite the site

Republishing press releases or third-party articles leaves dozens of nearly identical sources. A model may select the largest domain, the earliest source or a random page. Original experiments, expert commentary, specification tables, technical verification, event timelines, calculators and comparative datasets give a site a distinct role. The system obtains information unavailable elsewhere.

Cybersecurity reporting as a quality check

A cyber news item must enable an administrator to assess risk without hunting for missing details. Early paragraphs should state the product, vulnerable versions, operating conditions, required privileges, consequences, patched version and attack status. Three metrics serve different purposes: CVSS describes technical severity, EPSS estimates exploitation probability within 30 days, and the CISA KEV catalogue lists vulnerabilities with confirmed real-world exploitation.

A stable reporting template includes:

  • developer and exact product name
  • vulnerability identifier or bulletin number
  • affected and fixed versions
  • need for authorisation and network access
  • user actions, if any
  • consequences of successful attack
  • presence of proof-of-concept code
  • confirmation of real-world exploitation
  • primary advisory and practical recommendation

Technical accessibility and crawler management

Pages must return correct status codes and deliver main content in accessible HTML. Proper robots.txt directives, canonical URLs, sitemaps and internal linking remain essential. Googlebot handles indexing for Search and AI Overviews, Google-Extended controls training use, OAI-SearchBot manages ChatGPT search results, GPTBot is linked to possible training and Bingbot supports Bing and Copilot. Permission for one crawler does not imply permission for another.

IndexNow enables rapid notification of changes to Bing, Yandex and other partners, although Google does not support the protocol.

Measurement and new levers

Google Search Console now provides a separate report on generative visibility showing impressions in AI Overviews and AI Mode. Bing supplies citation metrics that include cited URLs and query intent. Owners are advised to track visibility, accuracy of reproduced facts and business outcomes such as clicks or conversions rather than citation counts alone.

When GEO becomes an attack vector

Optimisation techniques can be abused. Attackers may publish fabricated bulletins or pages containing hidden instructions. OWASP lists prompt injection among top LLM risks. Researchers at USENIX Security found non-existent package names in 5.2 percent of recommendations from commercial models and 21.7 percent from open models, enabling slopsquatting attacks that deliver malicious packages.

Sites handling high-stakes information therefore require primary documents, transparent correction policies and continuous monitoring of how generative systems paraphrase their content.

What is overrated

Files such as llms.txt are not recognised ranking signals by Google. Artificial segmentation of articles into micro-blocks or special “LLM Schema” markup brings no proven benefit. Only clarity, verifiable facts and original data reliably improve the chances that a source will be cited accurately.

Related articles

Habr•AI Security

TenetBench Benchmark Tests LLMs for Compliance with Professional Ethical Codes

Researchers from the Institute of Information Security Issues at ISP RAS and the Institute of Cybersecurity and Information Protection at RANEPA have developed TenetBench, a benchmark designed to evaluate how well large language models adhere to specific norms in professional codes of ethics. The benchmark generates realistic work-related prompts that may conflict with rules from documents such as the Code of Professional Ethics for Advocates or journalistic standards on undisclosed advertising. Each test case pairs a conflicting request with a neutral counterpart to measure whether models refuse, warn, or still provide prohibited content. Evaluation separates task completion, norm violation detection, and presence of explicit refusals using an LLM-as-a-Judge approach validated against human annotators. The full dataset contains 3,433 prompt pairs derived from 15 professional codes, with a public subset of 2,235 pairs from 10 documents. Human validation confirmed 99.5% of generated examples as fully plausible work scenarios.

AntiMalware•AI Security

Solar to Showcase Solar AI Firewall for Business Protection Against AI Risks at SOC Forum 2026

GK Solar will present its new Solar AI Firewall solution at SOC Forum 2026 to help organizations control interactions with AI services and prevent confidential data leaks through employee prompts. The product addresses growing risks from staff sending corporate data to neural networks and AI agents gaining access to internal systems. The forum takes place on 27-28 October in Moscow's Lomonosov cluster, with the official launch of Solar AI Firewall scheduled during the event. Solar will also highlight practical risks of AI adoption, including data transmission to external services, use of public models by employees, and new attack surfaces in corporate infrastructure. The solution will be demonstrated as part of an integrated ecosystem for access, network, and data protection. In addition, the company plans to introduce JSOC ONE, a new line of Solar JSOC services tailored for mid-sized businesses that require 24/7 monitoring without building their own SOC.

Habr•AI Security

Researcher Runs 100 Abliterated AI Agents Against His Own Accounts, Achieves Five Successful Breaches

A security researcher deployed roughly 100 autonomous AI agents based on abliterated open-source models to attempt unauthorized access to his online accounts over a five-hour period. The agents successfully compromised three accounts by exploiting vulnerabilities in legacy personal projects and two additional accounts through password reuse and credential stuffing. They also conducted 16 social engineering attempts, harvested and cross-verified personal data from public sources, and generated phishing pages targeting the researcher's Substack and Hacker News presence. Despite these successes, the agents failed to discover any zero-day vulnerabilities in third-party software or gain access to Tier-0 accounts such as Gmail, 1Password, or banking services. The experiment relied on abliterated versions of GLM-5.3 and DeepSeek V4 Flash models running on cloud GPUs, orchestrated via Codex CLI inside Docker containers with access to Railway infrastructure. Total compute cost reached approximately $210, equating to roughly $40 per successful account compromise. The researcher concluded that inexpensive swarms of such agents could soon enable low-skill attackers to systematically map and exploit an individual's entire online footprint.

Habr•AI Security

How Censorship in Closed AI Models Reshapes Science: Hugging Face Releases Open Carbon-X DNA Model

Hugging Face CEO Clement Delangue announced the release of Carbon-X, an open 14.8 billion parameter language model designed for reading, analyzing, and generating DNA sequences. The announcement highlighted how shallow guardrails in closed commercial models blocked even proofreading a tweet discussing the topic. Commenters and researchers pointed out that these input/output filters lack context awareness, blocking legitimate scientific queries while motivated adversaries bypass them through rephrasing. Carbon-X was built on Qwen3-14B with a hybrid BPE and 6-mer tokenizer, domain mid-training on 302 billion tokens, and safety achieved through data curation rather than runtime censorship. The model achieves performance comparable to closed frontier systems at roughly 1/1800th the inference cost for large-scale genomic tasks. The case underscores growing asymmetry between closed corporate AI labs building wet labs and independent researchers restricted by superficial safety layers.