Receber por email
← Voltar para o catálogo

azure-security-posture-hardening

Use esta skill para revisão da postura de segurança do Azure, endurecimento de linha de base, adoção de identidade gerenciada, postura do Key Vault, decisões de acesso privado, guardrails do Azure Policy e análise de lacunas de log ou auditoria. Acione-a quando o usuário perguntar como fortalecer uma carga de trabalho ou plataforma Azure sem recorrer a acesso amplo ou exposição pública.

19estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add Raishin/vanguard-frontier-agentic

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/azure-security-posture-hardening/svg)](https://www.skillteca.com.br/skills/azure-security-posture-hardening)
#ai

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Azure Security Posture Hardening

Purpose

Review and harden Azure platform or workload posture using operator-grade controls:

  • least privilege,
  • managed identities over stored secrets,
  • private access where justified,
  • Key Vault hardening,
  • policy-enforced controls,
  • audit and diagnostic coverage,
  • staged remediation with rollout safety.

When to use

Use this skill when the user asks for:

  • Azure security baseline or posture review,
  • managed identity migration guidance,
  • Key Vault hardening or secret-handling critique,
  • private endpoint or public exposure decisions for sensitive services,
  • Azure Policy or Defender-backed hardening recommendations,
  • logging, diagnostics, or auditability expectations for Azure security controls,
  • zero-trust-oriented review of platform or workload controls.

Do not use this skill as a full compliance audit, incident forensics runbook, or a substitute for deep service-specific implementation docs.

Lean operating rules

  • Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
  • [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
  • [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.
Compartilhar X LinkedIn