[GH-ISSUE #4963] [Feature Request]: Adding Custom Standards/Policies #2343

Closed
opened 2026-03-02 13:51:33 +03:00 by kerem · 2 comments
Owner

Originally created by @esrocom on GitHub (Nov 18, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4963

Please confirm:

  • I have searched existing feature requests (open and closed) and found no duplicates.
  • **me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

We already maintain internal baselines (for security, compliance, and operations) that are documented, reviewed, and audited. If we cannot model these baselines directly in CIPP, we end up with a gap between “what CIPP calls a standard” and “what our own procedures and documentation define as a standard”. Custom standards would allow us to keep CIPP and our internal documentation in sync, customers better secured, and perfectly alligned thanks to drift templates (by far one of the coolest features)

Benefits for MSPs

As we and other MSP's could develop new standards and make them available on github, cumulative knowledge about securing tenants can grow to a huge and easy-to-use thing and making MSP's less dependant on all the commercial products on the market.

Value or Importance

Less different dashboards for managing and securing customers boosts efficiency and cuts costs. A step closer to CIPP becoming the one and only central management tool.

PowerShell Commands (Optional)

No response

Originally created by @esrocom on GitHub (Nov 18, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4963 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement We already maintain internal baselines (for security, compliance, and operations) that are documented, reviewed, and audited. If we cannot model these baselines directly in CIPP, we end up with a gap between “what CIPP calls a standard” and “what our own procedures and documentation define as a standard”. Custom standards would allow us to keep CIPP and our internal documentation in sync, customers better secured, and perfectly alligned thanks to drift templates (by far one of the coolest features) ### Benefits for MSPs As we and other MSP's could develop new standards and make them available on github, cumulative knowledge about securing tenants can grow to a huge and easy-to-use thing and making MSP's less dependant on all the commercial products on the market. ### Value or Importance Less different dashboards for managing and securing customers boosts efficiency and cuts costs. A step closer to CIPP becoming the one and only central management tool. ### PowerShell Commands (Optional) _No response_
Author
Owner

@Zacgoose commented on GitHub (Nov 18, 2025):

Custom standards will not be allowed however any standards you want to see please make a feature request/s for them.

<!-- gh-comment-id:3547111381 --> @Zacgoose commented on GitHub (Nov 18, 2025): Custom standards will not be allowed however any standards you want to see please make a feature request/s for them.
Author
Owner

@KelvinTegelaar commented on GitHub (Nov 18, 2025):

Custom standards will not be allowrd as msps will use this to decrease the security of tenants. You can request any standard you'd like however

<!-- gh-comment-id:3547249639 --> @KelvinTegelaar commented on GitHub (Nov 18, 2025): Custom standards will not be allowrd as msps will use this to decrease the security of tenants. You can request any standard you'd like however
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#2343
No description provided.