docs(architect): weekly KB update — 66 files refreshed (2026-04)

Updated 66 stale knowledge base reference files (10 critical, 56 high)
across all 5 skills using Microsoft Learn MCP research.

Key factual updates:
- Groundedness Detection API: `correction` → `mitigating` param,
  `correctedText` → `correctionText` (breaking change)
- Copilot Studio: GPT-4.1 mini now default (was GPT-4o mini);
  Claude Sonnet 4.5 + Opus 4.5 added (experimental, 200K ctx)
- Agentic Retrieval: still public preview; 50M free tokens/month
- Azure security baselines: "Cognitive Services" → "Foundry Tools"
- Databricks: Delta Live Tables → Lakeflow Spark Declarative Pipelines
- MLflow 3 GenAI: new Feedback/Expectation data model
- Token tracking doc: "Azure OpenAI in Foundry Models through a gateway"
- Agent Registry: Risks column (M365 E7), Graph API (preview)
- Copilot DLP: new Entra AI Admin + Purview Data Security AI Admin roles
- ISO/IEC 42001: scope expanded to M365 Copilot, Foundry, Security Copilot
- Zero Trust: CAE now via Conditional Access, Strict Location Enforcement
- Purview: new Fabric Copilots/agents governance section
- AG-UI HITL: ApprovalRequiredAIFunction (C#), @tool approval_mode (Python)

All files: Last updated → 2026-04, *(Verified MCP 2026-04)* markers added.
Build registry: 1341 URLs from 387 files (+2 new URLs).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-04-09 22:41:26 +02:00
commit 565043dbde
73 changed files with 727 additions and 301 deletions

View file

@ -1,6 +1,6 @@
# AI Incident Response and Breach Handling Procedures
**Last updated:** 2026-02
**Last updated:** 2026-04
**Status:** Established Practice
**Category:** AI Security Engineering
@ -29,10 +29,11 @@ AI-systemer krever spesialiserte deteksjonsmekanismer utover tradisjonell SIEM-m
| **Adversarial Examples** | Input med lave confidence-scores på kjente data, batch-misklassifikasjoner | Model monitoring dashboards, drift detection |
| **Backdoor Attacks** | Targeted misklassifisering på spesifikke input-patterns, trojaned model artifacts | ML-BOM tracking (OWASP CycloneDX), supply chain audit |
**Microsoft-stack integrasjon:**
- **Microsoft Defender for AI Services** — Automatisk deteksjon av AI-spesifikke trusler (jailbreak, prompt injection) med MITRE ATLAS mapping
- **Azure AI Security Posture Management** — Kontinuerlig scanning av generative AI-risiko på tvers av Azure-miljøet
**Microsoft-stack integrasjon:** *(Verified MCP 2026-04)*
- **Microsoft Defender for AI Services / AI Security Posture Management** — Automatisk deteksjon og remediation av generative AI-risiko på tvers av Azure-miljøet (Microsoft Defender for Cloud)
- **Microsoft Purview Insider Risk Management** — Integrerer med andre security-suites for å vurdere enterprise-wide datarisiko og identifisere risky AI-atferdsmønstre og prompt-basert data exfiltration
- **Microsoft Sentinel AI/ML Analytics** — Custom KQL-queries for deteksjon av anomalous model behavior og data exfiltration-patterns
- **Azure API Management** — Sikrer Model Context Protocol (MCP) server-endepunkter som del av AI communication channel security
### 2. Response Playbooks (AI-Specific)
@ -487,6 +488,8 @@ Set-AzSecurityContact -Name "default1" `
1. **Incident Response Maturity**: "Har dere eksisterende incident response-planer, eller bygger vi fra scratch? Hvilke systemer er kritiske nok til å kreve 24/7 monitoring?"
*Tips (per CAF Secure AI 2026-04):* Bruk Azure Resource Graph til å bygge et komplett AI asset inventory som grunnlag for prioritering av monitoring-scope. *(Verified MCP 2026-04)*
2. **Compliance Requirements**: "Hvilke regulatoriske krav gjelder? GDPR (Datatilsynet 72h)? NSM-varsling? Sikkerhetsloven? Dette påvirker notification workflows og evidence retention."
3. **Current Detection Capabilities**: "Hvilke security tools er allerede i bruk? SIEM? EDR? Kan vi integrere, eller må vi deploye helt nye verktøy?"
@ -555,7 +558,7 @@ Set-AzSecurityContact -Name "default1" `
- [Microsoft Security Incident Management](https://learn.microsoft.com/en-us/compliance/assurance/assurance-security-incident-management) — Microsoft's internal federated security response model
**AI-Specific Security:**
- [Secure AI — Detect AI Security Threats](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/ai/secure) — AI-focused threat detection and incident response procedures
- [Secure AI — Detect AI Security Threats](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/ai/secure) — AI-focused threat detection and incident response procedures. Dekker: AI asset inventory (Azure Resource Graph), AI communication channel security (Managed Identities, Virtual Networks, APIM for MCP), data boundary definition (Microsoft Purview), DLP (Purview DLP + content filtering), og AI-spesifikk incident response (Defender for Cloud AI posture management). *(Verified MCP 2026-04)*
- [Threat Modeling AI/ML Systems](https://learn.microsoft.com/en-us/security/engineering/threat-modeling-aiml) — STRIDE + MITRE ATLAS mapping for AI threat landscape
- [AI/ML Pivots to SDL Bug Bar](https://learn.microsoft.com/en-us/security/engineering/bug-bar-aiml) — Severity classification for AI-specific threats (data poisoning, model inversion, etc.)