Repository navigation
Conversation
morri-son
force-pushed
the
ocm/add-neonephos-security-policy
branch
from
September 14, 2026 15:38
965cfb4 to
2102b81
Compare
4 tasks done
morri-son
force-pushed
the
ocm/add-neonephos-security-policy
branch
2 times, most recently
from
September 14, 2026 16:04
225370b to
de8fad8
Compare
frewilhelm
reviewed
Sep 15, 2026
frewilhelm
reviewed
Sep 15, 2026
morri-son
added a commit
to open-component-model/open-component-model
that referenced
this pull request
Sep 16, 2026
…iry date every year (#2386) ## Summary Add security.txt and a workflow to update it for Open Component Model vulnerability disclosure, aligned with NeoNephos Security Guidelines and CRA compliance requirements. **Important**: The organization-wide has been moved to a separate PR in the repository (see Related PRs below). This PR focuses on tooling, workflows, and security.txt updates only. ## Changes - ✅ Update `website/static/.well-known/security.txt` (RFC 9116 compliance) - Reference new reporting channels and contacts - Add Expires field with automated renewal workflow - ✅ Restore automated security.txt expiry renewal workflow - Runs every weekday in December at 09:00 UTC - Automatically updates Expires field to next year - Creates idempotent PR for review and merge - Ensures RFC 9116 compliance without manual maintenance - ✅ Security documentation references - Links to `docs/security/secure-design.md` - Links to `docs/security/assurance-case.md` ## Related PRs **⚠️ MERGE ORDER MATTERS:** 1. **FIRST**: Merge `open-component-model/.github#115` - Organization-wide SECURITY.md (applies to all repos) - NeoNephos Security Guidelines compliance - CRA stewardship statement per Linux Foundation - Commercial intent declaration - URL: open-component-model/.github#115 2. **THEN**: Merge this PR (`#2386`) - Security tooling and automation - security.txt updates **Reason**: The .github SECURITY.md is organization-wide and is referenced by this PR's security.txt updates. ## Compliance - ✅ RFC 9116 (security.txt standard) - ✅ NeoNephos Security Guidelines - ✅ CRA (EU Cyber Resilience Act) stewardship - ✅ DCO sign-off on all commits ## Test Plan - [x] Verify `security.txt` is valid per RFC 9116 - [x] Verify `security.txt` references correct SECURITY.md location - [x] Verify workflow runs correctly (manual trigger or wait for December) - [x] Verify Expires field updates to next year + 12-31 ## Closes - open-component-model/ocm-project#683 (security.txt automation) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Matthias Bruns <github@matthiasbruns.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
ocmbot Bot
pushed a commit
to open-component-model/open-component-model
that referenced
this pull request
Sep 16, 2026
…iry date every year (#2386) ## Summary Add security.txt and a workflow to update it for Open Component Model vulnerability disclosure, aligned with NeoNephos Security Guidelines and CRA compliance requirements. **Important**: The organization-wide has been moved to a separate PR in the repository (see Related PRs below). This PR focuses on tooling, workflows, and security.txt updates only. ## Changes - ✅ Update `website/static/.well-known/security.txt` (RFC 9116 compliance) - Reference new reporting channels and contacts - Add Expires field with automated renewal workflow - ✅ Restore automated security.txt expiry renewal workflow - Runs every weekday in December at 09:00 UTC - Automatically updates Expires field to next year - Creates idempotent PR for review and merge - Ensures RFC 9116 compliance without manual maintenance - ✅ Security documentation references - Links to `docs/security/secure-design.md` - Links to `docs/security/assurance-case.md` ## Related PRs **⚠️ MERGE ORDER MATTERS:** 1. **FIRST**: Merge `open-component-model/.github#115` - Organization-wide SECURITY.md (applies to all repos) - NeoNephos Security Guidelines compliance - CRA stewardship statement per Linux Foundation - Commercial intent declaration - URL: open-component-model/.github#115 2. **THEN**: Merge this PR (`#2386`) - Security tooling and automation - security.txt updates **Reason**: The .github SECURITY.md is organization-wide and is referenced by this PR's security.txt updates. ## Compliance - ✅ RFC 9116 (security.txt standard) - ✅ NeoNephos Security Guidelines - ✅ CRA (EU Cyber Resilience Act) stewardship - ✅ DCO sign-off on all commits ## Test Plan - [x] Verify `security.txt` is valid per RFC 9116 - [x] Verify `security.txt` references correct SECURITY.md location - [x] Verify workflow runs correctly (manual trigger or wait for December) - [x] Verify Expires field updates to next year + 12-31 ## Closes - open-component-model/ocm-project#683 (security.txt automation) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Matthias Bruns <github@matthiasbruns.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> 6579bd7
frewilhelm
previously approved these changes
Sep 17, 2026
morri-son
enabled auto-merge (squash)
September 17, 2026 10:30
matthiasbruns
approved these changes
Sep 17, 2026
Skarlso
approved these changes
Sep 17, 2026
morri-son
force-pushed
the
ocm/add-neonephos-security-policy
branch
2 times, most recently
from
September 17, 2026 12:21
767aadd to
0e6695c
Compare
…liance - Replace SAP security policy with Open Component Model specific policy - Reference NeoNephos Security Guidelines for standardized vulnerability handling - Add CRA stewardship statement per Linux Foundation requirements - Document commercial intent (required for CRA) - Include escalation contact for CRA (steward@linuxfoundation.org) - Align response timelines with NeoNephos standards (14 days initial, 90-day embargo) - Reference OpenSSF Best Practices alignment Signed-off-by: Gerald Morrison (D032990) <gerald.morrison@sap.com>
SECURITY.md is the org-wide default, so a hard-coded link to one repository's advisory list is wrong in every other repo. GitHub's org-wide advisory view is restricted to org owners/security managers, so replace the link with a per-repository placeholder URL and point readers to the Security tab of the affected repository. Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com>
Co-authored-by: Frederic Wilhelm <fre.wilhelm@gmail.com> Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com>
Signed-off-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com>
morri-son
force-pushed
the
ocm/add-neonephos-security-policy
branch
from
September 17, 2026 12:23
0e6695c to
3c06166
Compare
2 tasks done
morri-son
added a commit
to open-component-model/open-component-model
that referenced
this pull request
Sep 22, 2026
## Summary The org-wide [SECURITY.md](https://github.com/open-component-model/.github/blob/main/SECURITY.md) (merged via open-component-model/.github#115) now carries the OCM security policy aligned with the NeoNephos security guidelines. This PR links it from the website's security-reporting sections: - `community/_index.md`: Security section now also links the Security Policy directly. - `community/contributing.md`: Reporting section mentions the TSC email (`open-component-model-tsc@lists.neonephos.org`) as fallback channel and links the policy for supported versions, response targets, and the disclosure process. Refs open-component-model/ocm-project#683 ## Test plan - [x] markdownlint clean on both changed files (same config as CI) - [x] Hugo renders community pages (link check in CI) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
ocmbot Bot
pushed a commit
to open-component-model/open-component-model
that referenced
this pull request
Sep 22, 2026
## Summary The org-wide [SECURITY.md](https://github.com/open-component-model/.github/blob/main/SECURITY.md) (merged via open-component-model/.github#115) now carries the OCM security policy aligned with the NeoNephos security guidelines. This PR links it from the website's security-reporting sections: - `community/_index.md`: Security section now also links the Security Policy directly. - `community/contributing.md`: Reporting section mentions the TSC email (`open-component-model-tsc@lists.neonephos.org`) as fallback channel and links the policy for supported versions, response targets, and the disclosure process. Refs open-component-model/ocm-project#683 ## Test plan - [x] markdownlint clean on both changed files (same config as CI) - [x] Hugo renders community pages (link check in CI) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> 97a8af1
skarlso-release-bot Bot
pushed a commit
to Skarlso/open-component-model
that referenced
this pull request
Sep 22, 2026
…omponent-model#3633) ## Summary The org-wide [SECURITY.md](https://github.com/open-component-model/.github/blob/main/SECURITY.md) (merged via open-component-model/.github#115) now carries the OCM security policy aligned with the NeoNephos security guidelines. This PR links it from the website's security-reporting sections: - `community/_index.md`: Security section now also links the Security Policy directly. - `community/contributing.md`: Reporting section mentions the TSC email (`open-component-model-tsc@lists.neonephos.org`) as fallback channel and links the policy for supported versions, response targets, and the disclosure process. Refs open-component-model/ocm-project#683 ## Test plan - [x] markdownlint clean on both changed files (same config as CI) - [x] Hugo renders community pages (link check in CI) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> 97a8af1
ocmbotneisener Bot
pushed a commit
to jneisener/open-component-model
that referenced
this pull request
Sep 22, 2026
…omponent-model#3633) ## Summary The org-wide [SECURITY.md](https://github.com/open-component-model/.github/blob/main/SECURITY.md) (merged via open-component-model/.github#115) now carries the OCM security policy aligned with the NeoNephos security guidelines. This PR links it from the website's security-reporting sections: - `community/_index.md`: Security section now also links the Security Policy directly. - `community/contributing.md`: Reporting section mentions the TSC email (`open-component-model-tsc@lists.neonephos.org`) as fallback channel and links the policy for supported versions, response targets, and the disclosure process. Refs open-component-model/ocm-project#683 ## Test plan - [x] markdownlint clean on both changed files (same config as CI) - [x] Hugo renders community pages (link check in CI) --------- Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com> 97a8af1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Update the organization-wide SECURITY.md to align with NeoNephos Foundation security standards and EU Cyber Resilience Act (CRA) compliance requirements.
Changes
steward@linuxfoundation.orgCRA Compliance Details
Implementation Notes
This update follows the standardized approach adopted by all NeoNephos Foundation projects as of the September 2026 Linux Foundation guidance update. All commits include DCO sign-off for compliance audit trail.
Related