docs: Enhance security documentation with compliance and operational security details #130
+74
−0
Conversation
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
promptless
bot
requested review from
adit-chandra,
frances720,
mattlink and
prithvi2206
as code owners
Contributor
Author
|
I've added new changes to address this Slack mention in commit 5ecc666 |
Contributor
Author
|
I've added new changes to address this Slack mention in commit 72aa315 |
Contributor
|
don't really think i want to edit this actually |
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.
Adds six new sections to the Data Handling page addressing gaps in public security documentation: (1) SOC 2 Type II compliance certification, (2) Vulnerability management practices, (3) Audit logging and monitoring capabilities for enterprise customers, (4) Vendor security assessment processes, (5) Security program maintenance and annual reviews, and (6) Security incident reporting contact information. Each section is presented as a single concise sentence per Frances's request, providing transparency about Promptless's security posture while maintaining brevity and scannability.
Open this suggestion in the Promptless dashboard
Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)