Skip to content

chore(security): scope scanner configs to production code - #375

Open
rorymcentee wants to merge 1 commit into
masterfrom
repo-configure/scan-scope-20261113
Open

rorymcentee wants to merge 1 commit into
masterfrom
repo-configure/scan-scope-20261113

Conversation

@rorymcentee

Copy link
Copy Markdown

Adds the three ProdSec scanner scope files so Semgrep, Socket, and Fenceline only scan code that ships:

  • .semgrepignore — excludes non-production paths from Semgrep SAST (carries Semgrep's full default ignore list forward, then adds repo-specific dirs).
  • socket.yml — projectIgnorePaths so Socket SCA only ingests production manifest trees.
  • .fencelineignore — fenceline secrets FP suppression; findings under these paths are ledgered as DismissedByPath (never ticketed, skipped by revalidation). Note: already-ticketed records are untouched by this.

Ignored paths are limited to directories that actually exist in this repo (docs / fixtures / examples / test / storybook / public etc. — see the diff). Production trees (cmd, internal, src, packages, terraform roots) stay fully in scope.

Ref: Tier 1 scanner onboarding for the usetero org (github-deploy-tier1-prodsec-scanners).

Add .semgrepignore, socket.yml (projectIgnorePaths), and .fencelineignore
so Semgrep SAST, Socket SCA, and Fenceline secrets scans only cover
production code. Test/docs/fixture/example trees are excluded.
Part of the Tier 1 ProdSec scanner onboarding for usetero.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant