# Security Review

> Comprehensive security review of the Terraform provider codebase using gosec, trunk, osv-scanner, and trivy. Use when this capability is needed.

- Skill: `tomevault-io/security-review-29` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/security-review-29`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/security-review-29/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/security-review-29

---


# Security Review

This skill provides a systematic workflow for auditing the security of the Terraform Provider for Lightdash. It focuses on Go source code, dependencies, and secrets.

## Prerequisites

Ensure the following tools are installed and available in the PATH:

- `gosec` (Go Security Checker)
- `trunk` (Integrated linting and security platform)
- `osv-scanner` (Open Source Vulnerability Scanner)
- `trivy` (Vulnerability and secret scanner)

## Workflow

### 1. Static Analysis (SAST) for Go

Run `gosec` to identify common security pitfalls in Go code.

```bash
gosec ./internal/...
```

### 2. Integrated Security Check (via Trunk)

Run security-scoped checks using `trunk`. This includes tools like Semgrep and Gitleaks. We explicitly exclude `checkov` as per project preference.

```bash
trunk check --all --scope security --exclude checkov
```

### 3. Open Source Vulnerability Scan

Use `osv-scanner` to check for vulnerabilities in Go dependencies.

```bash
osv-scanner scan source -r .
```

### 4. Filesystem, Secret, and Config Scan

Use `trivy` to scan the filesystem for vulnerabilities, secrets, and misconfigurations (excluding Checkov-style IaC scans if redundant).

```bash
trivy fs . --scanners vuln,secret,config
```

## Reporting

After running these tools, synthesize the findings into a report with the following sections:

### 1. Summary of Findings

- Total issues found per tool.
- Breakdown by severity (Critical, High, Medium, Low).

### 2. Detailed Findings

For each significant finding, provide:

- **Tool**: Which tool reported it.
- **Location**: File path and line number.
- **Severity**: Reported severity.
- **Description**: Brief explanation of the risk.
- **Remediation**: Recommended fix or mitigation.

### 3. False Positives

Document any findings that are determined to be false positives and why.

### 4. Remediation Plan

Prioritize fixes based on severity and impact.

## Usage Note

Always run these checks before major releases or after significant architectural changes.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/ubie-oss) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->