Skip to content

Harden SecureCatch for public use - #1

Merged
cjcsecurity merged 1 commit into
securecatch-basefrom
fix/public-code-sample-hardening
Sep 17, 2026
Merged

cjcsecurity merged 1 commit into
securecatch-basefrom
fix/public-code-sample-hardening

Conversation

@cjcsecurity

Copy link
Copy Markdown
Owner

SecureCatch could expose domain-wide Gmail remediation and Jira mutations without authentication, its intake query was tied to one former environment, and the public repository lacked usable setup guidance or automated checks. This change makes the project safe to evaluate and practical to configure as an internal, single-administrator tool.

  • adds signed administrator sessions, route-level authorization, mutation-origin checks, and security headers
  • disables destructive remediation by default, requires exact ticket-key confirmation, and atomically claims actions
  • preserves partial purge results and surfaces mailbox or Jira failures instead of reporting false success
  • validates model JSON strictly and treats email/OSINT content as untrusted evidence
  • updates Jira ingestion to the current enhanced JQL API with pagination and a configurable query
  • fixes Google Alert Center matching and date selection
  • replaces starter docs and startup behavior with an operator-oriented setup path
  • upgrades Next.js, removes vulnerable SQLite adapter dependencies, adds tests and CI

Validation:

  • npm run check
  • npm audit --audit-level=high (0 vulnerabilities)
  • local HTTP integration covering login, route protection, mutation rejection, logout, and the remediation kill switch
  • gitleaks git . --redact --no-banner

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@cjcsecurity
cjcsecurity merged commit 216825f into securecatch-base Sep 17, 2026
3 checks passed
@cjcsecurity
cjcsecurity deleted the fix/public-code-sample-hardening branch September 17, 2026 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants