Copilot commented on code in PR #212: URL: https://github.com/apache/cloudstack-cloudmonkey/pull/212#discussion_r3568400089
########## SECURITY.md: ########## @@ -0,0 +1,35 @@ +<!-- +SPDX-License-Identifier: Apache-2.0 + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + https://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> + +# Security Policy + +## Reporting a Vulnerability + +`apache/cloudstack-cloudmonkey` follows the [Apache Software Foundation security process](https://www.apache.org/security/). +Please report suspected vulnerabilities privately to `[email protected]`; do not +open public GitHub issues or pull requests for security reports. + +## Threat Model + +`apache/cloudstack-cloudmonkey` is part of the Apache CloudStack project and is covered by the +**project-wide CloudStack threat model** rather than a per-repository copy. What the +project treats as in scope and out of scope, the security properties it provides and +disclaims, the adversary model, and how findings are triaged are documented in that +model: <https://github.com/apache/cloudstack/blob/main/THREAT_MODEL.md>. + +(That link resolves once the project-wide model lands on `apache/cloudstack`'s +`main` branch — see apache/cloudstack#13293. A thin `cloudstack-cloudmonkey`-specific +addendum can be added here later if this component needs one.) Review Comment: The threat model URL currently points to `apache/cloudstack/blob/main/THREAT_MODEL.md`, but that file does not exist on `apache/cloudstack`'s `main` branch yet (the link is a 404). This leaves a dead link in `SECURITY.md` and prevents automated scanners from reaching any threat model content today. Consider linking to a stable, currently-existing tracking location (or another canonical URL that resolves) until the project-wide threat model is actually published, then update back to the final file URL. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
