Skip to content
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

Update soc2 doc to point to Unleash Enterprise #8958

Merged
merged 2 commits into from
Dec 11, 2024

Conversation

ferrantim
Copy link
Collaborator

Was not clear that the Soc2 controls listed require Unleash Enterprise.

About the changes

Closes #

Important files

Discussion points

Was not clear that the Soc2 controls listed require Unleash Enterprise.
Copy link

vercel bot commented Dec 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 11, 2024 1:13pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ⬜️ Ignored (Inspect) Visit Preview Dec 11, 2024 1:13pm

Copy link
Contributor

github-actions bot commented Dec 11, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

@@ -9,7 +9,7 @@ description: 'SOC2-compliant feature flags at scale with Unleash.'

To get SOC2 certified and maintain your compliance, you must ensure that any system you integrate with, including feature flagging solutions, are also SOC2 certified. Using a homegrown or third-party feature flagging system without SOC2 compliance can compromise your certification and introduce unnecessary risks.

This guide provides an overview of how Unleash features align with SOC2 Type II controls, helping your organization meet its compliance requirements.
This guide provides an overview of how [Unleash Enterprise](https://www.getunleash.io/enterprise-feature-management-platform) features align with SOC2 Type II controls, helping your organization meet its compliance requirements.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to go ahead with this change, but technically not all the features we list in the table need Enterprise

@melindafekete melindafekete changed the base branch from main to ferrantim-fedramp-update December 11, 2024 12:59
@melindafekete melindafekete merged commit 7543125 into ferrantim-fedramp-update Dec 11, 2024
4 of 6 checks passed
@melindafekete melindafekete deleted the ferrantim-soc2-update branch December 11, 2024 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants