-
Notifications
You must be signed in to change notification settings - Fork 99
Initial commit for compliance reports in Platform Hub #3012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
ceacff0
Initial commit for compliance reports in Platform Hub
harrisonmeister d0e6c72
line edits
harrisonmeister 6be8d5a
Merge branch 'main' into mh/platform-hub-compliance
steve-fenton-octopus c7a537c
Apply suggestions from code review
harrisonmeister 411b924
Remove dashboard wording and replace with reports
harrisonmeister 2f4d6bb
Collapse two pages into one
TomPeters 30e128c
Updated copy
TomPeters cabdfc9
Add note about upcoming Production Deployments report
harrisonmeister 8b7c239
linting fix
harrisonmeister File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+105 KB
.../docs/img/platform-hub/compliance/deployment-permissions-report-choose-envs.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+115 KB
public/docs/img/platform-hub/compliance/deployment-permissions-report-executed.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| --- | ||
| layout: src/layouts/Default.astro | ||
| pubDate: 2026-01-21 | ||
| modDate: 2026-01-21 | ||
| title: Compliance | ||
| subtitle: An overview of the Compliance Dashboard | ||
| icon: fa-solid fa-shield-halved | ||
| navTitle: Overview | ||
| navSection: Compliance | ||
| description: An overview of the Compliance Dashboard | ||
| navOrder: 170 | ||
| --- | ||
|
|
||
| The Compliance Dashboard is a new addition to the Platform Hub, designed to transform raw audit data into actionable insights. | ||
|
|
||
| While you can already access granular logs via the [Audit](/docs/security/users-and-teams/auditing) tab or integrate with SIEM tools using the [audit stream](/docs/security/users-and-teams/auditing/audit-stream), the Compliance Dashboard streamlines reporting for Governance, Risk, and Compliance (GRC) teams. | ||
|
|
||
| Our initial reports focus on answering two critical questions: | ||
|
|
||
| 1. **Deployment Permissions**: Which users are authorized to deploy specific projects, and to which environments? | ||
| 2. **Production Deployments**: Who initiated deployments to Production, and when did those events occur? | ||
|
harrisonmeister marked this conversation as resolved.
Outdated
|
||
|
|
||
| Explore our available [Compliance reports](/docs/platform-hub/compliance/reports) to get started. | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| --- | ||
| layout: src/layouts/Default.astro | ||
| pubDate: 2026-01-21 | ||
| modDate: 2026-01-21 | ||
| title: Compliance reports | ||
| icon: fa-solid fa-clipboard-list-check | ||
| navTitle: Reports | ||
| navSection: Compliance | ||
| description: Available reports within the Compliance section of Platform Hub | ||
| navOrder: 172 | ||
| --- | ||
|
|
||
| Compliance reports in Octopus provide a centralized, audit-ready visibility into your software delivery lifecycle. They are designed to help Governance, Risk, and Compliance (GRC) teams quickly verify security controls and maintain a clear trail of deployment activity across your entire instance. | ||
|
|
||
| :::div{.hint} | ||
| Compliance reports are currently in Alpha. If you encounter any issues, please contact our [support team](https://octopus.com/support). | ||
| ::: | ||
|
|
||
| ## Deployment Permissions | ||
|
|
||
| The Deployment Permissions report provides a comprehensive map of access across your instance, allowing you to audit which users and teams possess the authority to trigger deployments. By cross-referencing user roles with specific projects and environments, this report helps GRC teams validate that the principle of least privilege is being enforced and ensure that only authorized personnel can influence your release pipeline. | ||
|
harrisonmeister marked this conversation as resolved.
Outdated
|
||
|
|
||
| ### Running the report | ||
|
|
||
| To run the Deployment Permissions report, navigate to **Platform Hub -> Reports**, and choose the **Deployment Permissions** tile: | ||
|
harrisonmeister marked this conversation as resolved.
Outdated
|
||
|
|
||
| :::figure | ||
|  | ||
| ::: | ||
|
|
||
| Select one or more environments from your Octopus Spaces to view Deployment permissions for: | ||
|
|
||
| :::figure | ||
|  | ||
| ::: | ||
|
|
||
| Finally, click on the **Create Report** button and view the projects for the selected environments, and the users that can deploy to each project in that environment: | ||
|
|
||
| :::figure | ||
|  | ||
| ::: | ||
|
|
||
| You can expand each project to see a list of the users that have permissions to deploy to that environment. You can also click the **Download CSV** button to generate a CSV file of the executed report. | ||
|
|
||
| ## Production Deployments | ||
|
|
||
| :::div{.hint} | ||
| The Production Deployments report is currently under development, and will be ready soon. | ||
|
harrisonmeister marked this conversation as resolved.
Outdated
|
||
| ::: | ||
|
|
||
| This report is designed to provide a definitive audit trail of all activity within your most sensitive environments. It will offer a streamlined view of who initiated changes to Production and precisely when they occurred, facilitating effortless point-in-time compliance reviews. | ||
|
|
||
| ## Feedback | ||
|
|
||
| We'd love to get [feedback on what reports you need](https://roadmap.octopus.com/submit-idea) to make compliance easier! | ||
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.
Uh oh!
There was an error while loading. Please reload this page.