Versioned security assessment

Report ID: SA-68608210

6/28/2026, 5:51:28 AM

policy-opa security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
policy-opa
Version
v6
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/compliance/policy-opa
Coverage
14 Files scanned · 3,721 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Low

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static analysis reported many high-severity patterns, but review found no prompt injection, malware behavior, or credential exfiltration. Most hits are false positives from Rego policy examples, compliance terms, public reference URLs, and defensive security vocabulary. The skill is medium risk because CI examples run shell commands and download OPA over the network, which users should review before copying into pipelines.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

14 Files scanned · 3,721 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 5 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Capability review items (3)
Medium
assets/ci-cd-pipeline.yaml:31assets/ci-cd-pipeline.yaml:166assets/ci-cd-pipeline.yaml:214
CI Examples Execute Shell Commands and External Tools
Verdict: TRUE_POSITIVE. The GitHub and GitLab CI examples use shell command substitution, Terraform, jq, curl, and OPA commands. This is legitimate for a policy-as-code skill, but copied pipelines can execute in privileged CI contexts and should be reviewed before use.
The executable shell patterns are directly present in CI YAML. The commands are ordinary OPA and Terraform workflow commands, so the risk is operational rather than malicious.
Medium
assets/ci-cd-pipeline.yaml:107assets/ci-cd-pipeline.yaml:220references/iac-policies.md:612
Terraform Plan Examples May Process Sensitive Deployment Data
Verdict: NEEDS_REVIEW. The examples generate Terraform plan JSON and evaluate it with OPA. Terraform plan data can include sensitive values depending on provider behavior, so CI logs and artifacts should avoid exposing raw plan contents.
The files show Terraform plan evaluation, but they do not show secrets being printed or uploaded. The sensitivity depends on the user repository and CI configuration.
Low
SKILL.md:19-21references/iac-policies.md:320-330references/kubernetes-security.md:547-550
Public URLs and Example Network Ranges Are Benign References
Verdict: FALSE_POSITIVE. Most hardcoded URLs are public documentation links, and 0.0.0.0/0 appears as an insecure network range that policies detect. These examples do not exfiltrate data.
The URLs point to public project or standards documentation, and the IP range is part of a policy rule detecting open ingress. No outbound data transfer logic is present.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 Low
assets/soc2-compliance.rego:1-5assets/terraform-security.rego:54-78references/compliance-frameworks.md:3-7
Rego Security Keywords Misclassified as Malicious Indicators
Verdict: FALSE_POSITIVE. Terms such as deny, control, encryption, privileged, and network appear in defensive OPA policies. They describe controls that block insecure Kubernetes, Terraform, SOC2, PCI-DSS, and GDPR configurations.
The surrounding context is Rego policy authoring and compliance mapping. No command-and-control behavior or malicious instructions were found.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
SKILL.md:36-46references/rego-patterns.md:18-25references/kubernetes-security.md:19-37
Markdown Code Fences Misclassified as Ruby Backtick Execution
Verdict: FALSE_POSITIVE. Static analysis flagged many fenced Rego and YAML examples as backtick execution. These are documentation blocks, not Ruby strings or executable code in the skill runtime.
The files are Markdown references with fenced examples. Some examples can be copied by users, but they are not hidden execution paths inside the skill.
Low
assets/k8s-pod-security.rego:3-4assets/k8s-constraint-template.yaml:32-33assets/gdpr-compliance.rego:3
Future Keyword Imports Misclassified as Certificate or Key Files
Verdict: FALSE_POSITIVE. Static analysis treated Rego import statements containing future.keywords as certificate or key references. These imports enable Rego syntax features and do not read secrets or key material.
The referenced lines are Rego imports, not file paths, PEM data, private keys, or certificate loaders. This is a clear lexical false positive.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable