Skip to content

chore: repository hygiene for SOC 2 readiness - #17

Open
hmolavi wants to merge 5 commits into
mainfrom
hcook-soc2-hygiene
Open

hmolavi wants to merge 5 commits into
mainfrom
hcook-soc2-hygiene

Conversation

@hmolavi

@hmolavi hmolavi commented Sep 26, 2026 •

Copy link
Copy Markdown

What

  • .github/dependabot.yml: weekly version updates for uv and github-actions. Minor and patch updates are grouped per ecosystem, at most 5 open pull requests each.
  • SECURITY.md: reports go to security@scadable.com and get a reply within five business days, the time the Vulnerability and Patch Management Policy (section 4.3) promises an outside reporter and the one scadable/landing#11 and scadable/trust-manager#41 publish. No bug bounty.
  • .github/CODEOWNERS: new, * @scadable/founders.

Why

SOC 2 readiness (claude-plans soc2-readiness-01, item A12). Makes the evidence checks repository_dependabot_config_present, repository_has_codeowners_file and repository_public_has_securitymd_file pass for this repository. No repository or organization setting is changed.

Owner steps (not done here)

  1. Create the founders team, visible, with write access to this repository. The org has no teams today, so GitHub reports every @scadable/founders line as an unknown owner.
  2. Turn on Dependabot security updates. CodeQL default setup, secret scanning, push protection and Dependabot alerts are already on here.

Checks run

  • .github/dependabot.yml parses with PyYAML and with evidence's strict YAML subset, and evidence's validate_dependabot finds no problems (every ecosystem is backed by a file in its directory).
  • check-jsonschema against the SchemaStore Dependabot schema: pass.
  • Independent review (2026-09-25): facts re-checked against the repositories, GitHub and the live Workload Identity bindings; the Dependabot and workflow gates re-run and passing. Two fixes pushed: SECURITY.md now promises the policy's five business days instead of one, and the Dependabot header no longer says nothing merges without a review, since no branch protection requires one yet.

Weekly updates for the package ecosystems this repository uses, minor and
patch grouped per ecosystem, at most five open pull requests each.
Reports go to security@scadable.com and are acknowledged within one
business day, the promise the trust center makes. No bug bounty.
A catch-all rule for @scadable/founders, above any existing narrower rules.
The Vulnerability and Patch Management Policy (section 4.3) promises an
outside reporter a reply within five business days, and scadable.com/security
and the trust center seed (landing#11, trust-manager#41) say the same. One
business day was a promise no policy backs. What to include now matches the
website, and the file promises only what the policy does.
No branch protection requires a review yet, so the header no longer says
nothing merges without one. It says instead that Dependabot only opens pull
requests, and, where the file has one, that the GitHub Actions entry groups
every update, majors included.
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.

1 participant