Skip to content

CrashBytes/claude-role-skills / skills/infosec-engineer

infosec-engineer

Verified

Act as an Information Security Engineer to conduct security assessments, threat modeling, vulnerability analysis, compliance reviews, and incident response planning. Use when users need help with security architecture review, threat modeling (STRIDE, DREAD, attack trees), vulnerability assessment, OWASP Top 10 remediation, secure code review, compliance frameworks (SOC 2, ISO 27001, HIPAA, PCI DSS, GDPR), incident response planning, security policy creation, penetration test scoping, or security hardening. Trigger on mentions of security review, threat model, vulnerability, OWASP, compliance, incident response, security policy, penetration testing, hardening, or security architecture.

FileKindSize
LICENSE.txtmarkdown11.1 KB
SKILL.mdskill md11.1 KB
references/compliance-controls.mdmarkdown4.3 KB
references/integrations.mdmarkdown3.8 KB
references/owasp-remediation.mdmarkdown8.9 KB
references/policy-templates.mdmarkdown8.6 KB

references/integrations.md

View on GitHub
# Security Tool Integrations

This skill works best when connected to development and security platforms via MCP (Model Context Protocol) servers. MCP servers give Claude direct access to repositories, pipelines, issues, and security findings.

Browse available servers: [MCP Registry](https://registry.modelcontextprotocol.io)

## Detecting Available Integrations

Before performing security actions, check what tools are available:

1. **MCP servers** — If GitHub, GitLab, Azure DevOps, or Jira MCP servers are connected, use them directly
2. **CLI tools** — Fall back to `gh`, `glab`, `az`, `trivy`, `npm audit`, `pip-audit` via Bash
3. **Manual input** — If no integrations detected, ask the user to provide data or suggest connecting an MCP server

## GitHub

**Official:** [github/github-mcp-server](https://github.com/github/github-mcp-server)

```bash
claude mcp add github -- npx -y @modelcontextprotocol/server-github
```

Requires `GITHUB_PERSONAL_ACCESS_TOKEN` env var.

**InfoSec actions:** Review PR diffs for security vulnerabilities, query Dependabot alerts, manage security advisory issues, review GitHub Actions workflows for CI/CD security gaps, check branch protection rules, audit repository access permissions.

## GitLab

**Official:** [GitLab MCP Server](https://docs.gitlab.com/user/gitlab_duo/model_context_protocol/mcp_server/)

```bash
claude mcp add gitlab -- npx -y @modelcontextprotocol/server-gitlab
```

Requires `GITLAB_PERSONAL_ACCESS_TOKEN` and `GITLAB_API_URL` env vars.

**InfoSec actions:** Review merge requests for security issues, query vulnerability reports, manage security-labeled issues, review CI pipeline security scan results, audit project-level access controls.

## Azure DevOps

**Official:** [microsoft/azure-devops-mcp](https://github.com/microsoft/azure-devops-mcp)

```bash
claude mcp add azure-devops -- \
  npx -y @microsoft/azure-devops-mcp-server \
  --organization your-org --project your-project
```

Requires `AZURE_DEVOPS_PAT` env var.

**InfoSec actions:** Query security-related work items, review build pipeline configurations for hardening gaps, track security bug resolution SLAs, manage compliance-related test plans, audit pipeline permissions and approvals.

## Jira / Atlassian

**Official:** [atlassian/atlassian-mcp-server](https://github.com/atlassian/atlassian-mcp-server)

```bash
claude mcp add atlassian-mcp-server \
  --transport streamable-http \
  --url https://mcp.atlassian.com/v1/sse
```

**InfoSec actions:** Track vulnerability remediation workflows, manage incident response tickets, query security policy documents in Confluence, track compliance audit findings, manage penetration test result tickets.

## Pusher Channels (Incident Communication)

**Registry:** [Pusher MCP on registry](https://registry.modelcontextprotocol.io/?q=pusher&all=1)

```bash
claude mcp add pusher -- npx -y @AshDevFr/pusher-channels-mcp-server
```

Requires `PUSHER_APP_ID`, `PUSHER_KEY`, `PUSHER_SECRET`, `PUSHER_CLUSTER` env vars.

**InfoSec actions:** Send real-time incident alerts to security channels, broadcast security status updates during active incidents, trigger automated notification workflows for severity escalations, monitor security event streams.

## Integration Detection Pattern

When a user asks for help with security reviews, compliance, or incident response:

1. Check if any development platform MCP servers are available
2. If yes, use them to review code for vulnerabilities, manage security issues, and audit configurations
3. If no MCP tools available, check for security CLI tools (`trivy`, `npm audit`, `pip-audit`, `bandit`)
4. If nothing available: "I can connect to your development and security platforms via MCP server — see the [MCP Registry](https://registry.modelcontextprotocol.io). Otherwise, share your code or findings and I'll analyze them."
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall