04 Ноя, 2025

Artificial intelligence as a threat and a tool

Artificial intelligence (AI) simultaneously expands the offensive toolkit of threat actors and strengthens the defender’s capabilities across detection, response, and governance. This research paper examines both sides through a cybersecurity lens: (1) how AI amplifies social engineering, intrusion operations, and attacks on AI systems themselves; and (2) how AI can be operationalized responsibly as a security instrument. We synthesize current guidance and frameworks (NIST AI RMF, OWASP GenAI, ENISA, MITRE ATLAS), recent incidents (e.g., deepfake-enabled fraud), and regulatory shifts (EU AI Act) to propose a practical roadmap for CISOs.

Executive summary — key findings

• AI as a threat multiplier. Generative models scale social engineering (voice/face deepfakes, hyper‑personalized lures) and accelerate reconnaissance and tooling. Attacks against AI stacks (prompt injection, data/model poisoning, model theft) have moved from theory to practice.

• AI as a defensive co‑processor. Modern SOCs use AI to triage alerts, summarize telemetry, reverse‑engineer malware, and supercharge analysts. When paired with strong guardrails and human oversight, this improves speed and coverage without automating risk decisions.

• Supply chain risk extends to models and datasets. Malicious or trojaned models and insecure serialization (e.g., unsafe pickle) can backdoor developer workstations and pipelines; scanning, signing, and isolated inference are now table‑stakes.

• Governance is catching up. The EU AI Act entered into force on 1 Aug 2024. Prohibitions and AI‑literacy duties applied from Feb 2025; GPAI obligations from Aug 2025; broader application phases continue into 2026–2027.

• Security-by-design for AI is no longer optional. Joint NCSC/CISA guidelines, NIST AI RMF + GenAI Profile, and ISO/IEC 42001 define concrete practices for robust, transparent and governable AI systems.

1) Scope and definitions

We distinguish three related but different topics:

• AI‑enabled attacks: adversaries using AI to increase scale, speed or quality of existing TTPs (e.g., spear‑phishing, fraud, tooling).

• Attacks on AI systems: targeting the model/application/data/infra (e.g., prompt injection, model theft, data or model poisoning, evasion).

• AI for cyber defense: augmenting detection, response, engineering, and governance workflows with AI (with human‑in‑the‑loop).

2) AI as a threat

2.1 Deepfakes & social engineering

Synthetic media lowers the cost of convincing fraud. In Feb 2024, a finance worker in Hong Kong was duped during a video call where every participant (including a fake CFO) was an AI‑generated deepfake—HK$200 million (~US$25.6 million) was wired before the ruse was discovered. National authorities and independent testers warn that deepfakes, voice cloning and generative text increase the believability and volume of phishing and business‑email compromise (BEC), challenging traditional awareness training and filters.

2.2 Augmented intrusion campaigns

Multiple governments and vendors have reported early but real use of generative AI by state‑aligned actors for reconnaissance, phishing content, and research support—not yet “new classes” of attacks, but observable scaling and localization of existing ones. Expect AI to steadily raise baseline capability for criminal groups as tooling matures.

2.3 Risks in LLM‑powered applications (OWASP)

The OWASP GenAI project maintains a living Top 10 for LLM applications. Key risks include: prompt injection and data exfiltration; insecure output handling (e.g., blindly executing generated code); poisoning of training/fine‑tuning/embedding data; model DoS and excessive agency in agentic systems; insecure plugin/tool design; over‑reliance and model theft.

2.4 Adversarial machine learning (attacks on models)

Beyond application‑level issues, ML models are vulnerable to evasion (adversarial examples at inference), poisoning (corrupting training or embedding data), privacy attacks (inversion, membership inference), and extraction (stealing parameters/behavior). NIST’s taxonomy and MITRE ATLAS catalog these tactics and mitigations; ENISA synthesizes European perspectives.

2.5 Model & data supply chain

Model hubs and pipelines introduce new supply‑chain risk. Researchers have identified malicious models that executed code via unsafe serialization or embedded payloads; platform maintainers have since expanded scanning and safer formats, but enterprises must “trust but verify” by scanning, signing, and isolating models in runtime containers.

2.6 RAG and agentic patterns

Retrieval‑augmented generation (RAG) improves factuality but increases the attack surface via indirect prompt injection (malicious instructions in retrieved content), index poisoning, and leakage of sensitive data through vector stores. Recent demonstrations show email/Gmail summarizers and enterprise assistants can be manipulated via HTML/CSS‑hidden prompts unless robust filters and isolation are used. OWASP now documents vector/embedding weaknesses explicitly.

3) AI as a defensive tool

• SOC copilots. Generative AI can summarize alerts, explain detections, draft KQL/Splunk queries, and accelerate case hand‑offs—Microsoft commercialized this pattern as “Copilot for Security” in April 2024.

• Malware analysis. Long‑context models (e.g., Gemini 1.5) assist with rapid triage of decompiled code, function labeling, and behavior hypotheses—useful as a second reader, not a final verdict engine.

• Threat intel & hunting. AI helps normalize heterogeneous intel, enrich IOCs, and draft YARA/Sigma hypotheses for human review, boosting coverage and time‑to‑insight.

• Secure engineering. Pair LLMs with SAST/DAST/IAST to explain findings, suggest safer APIs, and generate tests—while enforcing repository‑level secrets scanning and pre‑commit policies (per NIST SSDF).

4) Security architecture & controls for AI

4.1 Secure‑by‑design for AI (build time)

Follow NCSC/CISA’s Guidelines for secure AI system development (threat modeling, data provenance/quality, supply‑chain control, red teaming, secure deployment).

Adopt NIST AI RMF functions—GovernMapMeasureManage—and the Generative AI Profile for concrete actions (eval, safety, resilience).

Apply NIST SSDF to AI code and orchestration layers; treat model gateways like critical services (SBOMs, dependency pinning, reproducible builds).

4.2 Isolation & guardrails (runtime)

Isolate model execution (containers/VMs), restrict egress, and allowlist tools the model/agent may invoke. Never grant shell or cloud root.

Validate outputs before action (policy engines, regex/AST checks, sandbox execution); treat all retrieved/context inputs as untrusted.

Segment prompts/context by user and task; scrub secrets/PII on ingestion; enforce token/credential scoping and rotation.

4.3 RAG/agent hardening

Filter/normalize retrieved content (strip hidden HTML/CSS, URLs, JavaScript, and “instructions-as-data”); add content provenance headers to context chunks.

Protect vector stores with per‑document ACLs; avoid global embeddings where access controls are lost; monitor for anomalous embeddings.

Prefer live connectors that preserve source authorization over bulk-copied corpora; if centralizing, enforce data minimization and retention.

4.4 Model & data provenance

Scan all models/datasets; prefer safetensors or similarly safe formats; require signatures/attestations; run in restricted sandboxes.

Adopt Content Credentials (C2PA) to embed signed provenance in media your org produces; build trust signals into review/approval flows.

4.5 Evaluation, testing & monitoring

Establish continuous red‑teaming (prompt injection, jailbreaks, data leakage); track regression metrics; log and review model/tool telemetry.

Define tripwires (e.g., abnormal tool usage, exfil patterns, surge in toxic outputs) that automatically suspend risky automation for human review.

5) Governance & compliance

EU AI Act — what security leaders need to know

• Entry into force: 1 Aug 2024. First obligations: prohibitions + AI literacy from 2 Feb 2025; GPAI obligations: from 2 Aug 2025.

• General date of application: most provisions apply from 2 Aug 2026; the Act is expected to be fully effective by 2027, with standards and codes assisting implementation.

• GPAI cybersecurity duties: providers of systemic‑risk GPAI must assess and mitigate risks (including cybersecurity), report serious incidents, and implement model security protections.

Standards to align with

• NIST AI RMF 1.0 (+ Generative AI Profile) for risk management.

• ISO/IEC 42001:2023 for an AI management system (AIMS)—governance processes that complement security controls.

• ENISA Threat Landscape for EU‑oriented threat trends and mitigations.

6) A pragmatic 90‑day roadmap

DaysWhat to doWhy it matters
0–30Inventory AI use cases, models, connectors, and datasets. Classify by business impact and data sensitivity. Stand up a lightweight AI governance group (security, legal, risk, product). Adopt AI RMF roles and risk register.Establish scope, owners, and risk language.
31–60Implement guardrails: model/agent allowlists, scoped credentials, output validation, egress controls, prompt and tool logging. Pilot red‑teaming against OWASP LLM Top 10.Reduce blast‑radius and capture telemetry.
61–90Harden RAG/agents: sanitize retrieved content; tighten vector‑store ACLs; deploy model/dataset scanning and signing; set provenance (C2PA) for media. Map to AI Act and ISO 42001 controls; brief execs on obligations and timelines.Address dominant enterprise risks and compliance gaps.

7) Metrics that matter

• Time saved per analyst task (triage, correlation, reporting) with human quality checks.

• Guardrail efficacy: % of blocked prompt‑injection attempts; # of unsafe outputs caught pre‑execution.

• Provenance coverage: % of outbound media with C2PA credentials; % of models/datasets scanned and signed.

• RAG hygiene: % of retrieved chunks sanitized; % of vector docs with correct ACLs; retrieval precision@k.

• Compliance readiness: AI RMF/ISO 42001 control coverage; status vs. AI Act milestones.

8) CISO checklist — do now

Appoint accountable owners for AI security and governance; publish decision rights.

Ban unsanctioned model downloads; enforce model/dataset scanning and signature verification.

Segregate model runtime; allowlist tools/APIs; log prompts, context, and tool calls end‑to‑end.

Deploy prompt/response filters; strip hidden content from retrieved data; sandbox any generated code.

Enable Content Credentials (C2PA) on outbound media workflows; train staff on verification.

Stand up continuous red‑teaming and abuse‑testing for LLM apps (aligned to OWASP/ATLAS).

Map obligations to AI Act/ISO 42001; track deadlines (Feb 2025, Aug 2025, Aug 2026).

References

  1. NIST AI RMF 1.0 — PDF. nvlpubs.nist.gov
  2. OWASP GenAI — Top 10 for LLM Applications (live project). owasp.org
  3. MITRE ATLAS — adversarial threat landscape for AI systems. atlas.mitre.org
  4. ENISA Threat Landscape 2024 — PDF. enisa.europa.eu
  5. Microsoft Copilot for Security — GA (Apr 1, 2024). microsoft.com
  6. Google Cloud — Malware analysis with Gemini 1.5. cloud.google.com
  7. BleepingComputer — Malicious AI models on Hugging Face. bleepingcomputer.com
  8. The Hacker News — Hugging Face supply‑chain risk (safetensors pipeline). thehackernews.com
  9. European Commission — AI Act enters into force (Aug 1, 2024). commission.europa.eu
  10. EC Fact Page — GPAI obligations apply from Aug 2, 2025. digital-strategy.ec.europa.eu
  11. Simmons & Simmons — AI Act key dates (prohibitions Feb 2, 2025). simmons-simmons.com
  12. NCSC (UK) & CISA — Guidelines for secure AI system development (PDF). ncsc.gov.uk
  13. CISA alert — Joint guidance on deploying AI systems securely. cisa.gov
  14. ISO/IEC 42001:2023 — AI management systems. iso.org
  15. SCMP — HK$200 million deepfake video‑call fraud (Feb 2024). scmp.com
  16. Financial Times — Arup deepfake case follow‑up. ft.com
  17. The Guardian — NCSC warns AI will boost phishing. theguardian.com
  18. Washington Post — Platforms inconsistently surface C2PA credentials (2025 test). washingtonpost.com
  19. AP News — Generative AI in offensive ops (Microsoft/OpenAI report). apnews.com
  20. NIST — Adversarial ML taxonomy (AI 100‑2; 2023/2025 updates). csrc.nist.gov
  21. ENISA — Securing ML algorithms (threats & mitigations). enisa.europa.eu
  22. Hugging Face + Protect AI — model scanning partnership. huggingface.co
  23. TechRadar — Prompt‑injection risks in email summarization. techradar.com
  24. Microsoft MSRC — Adaptive prompt injection challenge (LLMail‑Inject). microsoft.com
  25. OWASP GenAI — Prompt Injection (LLM01) and Vector/Embedding Weaknesses. genai.owasp.org
  26. OWASP GenAI — Vector & Embedding Weaknesses. genai.owasp.org
  27. Microsoft — Copilot for Security GA blog. microsoft.com
  28. CSO Online — Copilot for Security coverage. csoonline.com
  29. Google Cloud blog — Scaling up malware analysis with Gemini 1.5 Flash. cloud.google.com
  30. NIST SP 800‑218 — Secure Software Development Framework (SSDF). csrc.nist.gov
  31. NIST — Generative AI Profile (AI 600‑1). nvlpubs.nist.gov
  32. C2PA — open standard for content provenance. c2pa.org
  33. Google — adopting C2PA across products. blog.google
  34. TikTok — auto‑flagging AI videos with C2PA watermarks (news coverage). theguardian.com
  35. European Parliament EPRS — AI Act implementation timeline (PDF). europarl.europa.eu
  36. KPMG (overview) — ISO/IEC 42001 certification explainer (2025). kpmg.com

Другие Услуги

Готовы к безопасности?

Связаться с нами