Reposting this from the JumpCloud Slack Lounge on behalf of
@NeerajK:
Hello JumpCloud Community Members,We're excited to share a new initiative in our journey towards Device Compliance - one that's tailored to your needs and simplifies compliance management. As valued members of our community, we want your insights!
๐ The Approach We're Exploring:In the initial phase of the project, we're focusing on a device compliance approach centered around policy groups. This will allow you to collectively assess the compliance posture of your device fleet based on the policies assigned to them. This approach aims to provide you with a flexible way to manage compliance across your device fleet and easily report this to stakeholders.
๐ Looking Ahead to Subsequent Phases:But that's just the beginning. For future phases, we're exploring the incorporation of industry benchmarks like CIS and introducing application-level Allow/Deny compliance for devices to monitor unauthorized software on devices. Additionally, we're investigating leveraging device compliance posture for conditional access.We're particularly interested in how these potential enhancements align with your needs and priorities.
๐ข We're Eager to Hear:
- How well does our new device compliance approach resonate with your organization's compliance needs and workflow?
- What potential benefits do you see in this approach, and are there any concerns or adjustments you think might be necessary?
- How does the concept of industry benchmark support and application allowlisting and denylisting Compliance align with your organization's compliance or security goals?
- Could you share specific scenarios where these new compliance features would prove valuable for your organization?
- Are there any suggestions or features you'd recommend to enhance the usability and effectiveness of this device compliance feature?
Please take a moment to share your thoughts! Your feedback drives our innovation, and we're grateful for your contribution.
