Feedback Ideas

This has been asked/requested by a few, so building a feedback item here for further input and research. Why it matters: Some laws and standards (like HIPAA for healthcare or PCI-DSS for payment systems) say you must encrypt personal or sensitive data to keep it safe from hackers or leaks.Encrypting inside NIM: You should be able to choose specific fields in your system tables (like passwords or SSN) and encrypt them using a key that only NIM admin controls. This keeps the data safe even if someone gets access to the database.Encrypting exported data: If you export data from NIM (for reports, backups, or sharing with partners), allow the file to be encrypted using an admin-provided key. That way, the data stays protected even outside the system. Recommendations per industry standards Use secure connections: Always send data over HTTPS with the latest version of TLS (like TLS 1.2 or 1.3). This keeps the data encrypted while it’s traveling.Strong encryption: Use trusted methods like AES-256 (for encrypting data) and RSA (for sharing keys securely). These are widely accepted and hard to break.Protect your keys: Store encryption keys in secure places like a key vault or hardware security module. Rotate them regularly and limit who can access them.Verify the data: Add digital signatures or checksums so the receiving system can confirm the data wasn’t changed or tampered with.Follow the rules: Make sure you’re meeting standards like GDPR (for privacy), NIST (for government systems), or ISO 27001 (for general security). These help you stay compliant and avoid fines

It would be nice to be able to structure & reorder roles either through folders, or child roles akin to filters.

There would be some potential benefit in having an Admin Dashboard when you login to the NIM Studio. Essentially providing an overall health status for the service. Here are some key items you would see System/Filters/Jobs/Scheduler StatusesLicense StatusBackup StatusConnector/Service UpdatesConfiguration RecommendationsRecent Error logs Attached is a concept of the information that could be presented

Integrated with KnowBe4

In our environment, we have an OU that contains a very large number of user objects that aren’t real people. These objects represent device MAC addresses and are created automatically by a legacy network access control process. Our network policy servers use group membership on these objects to allow or deny devices access to the network and apply VLANs/ACLs. Because of this, the OU contains over ~70,000 non-human user objects that don’t participate in onboarding, offboarding, or any identity lifecycle workflows. Including them in NIM adds a lot of unnecessary clutter and makes it harder to search for actual users, especially in areas with limited filtering options. Having a supported way to ignore or exclude specific OUs (and their sub-OUs) would reduce noise and make administration much easier.

Used by count for relationships is always 0, should it be?

NIM currently supports only two access levels: FULL or APPS-only. It would be helpful to have an "admin light" security level for junior admins to manage existing source syncs and run existing schedules/jobs when needed, but not be able to make changes to role model, mappings, filters, or what-have-you.

A proposed enhancement to the product is the introduction of workflows, allowing requests to be reviewed and approved by designated reviewers before proceeding. This would be particularly beneficial in scenarios such as application access requests or provisioning processes, ensuring oversight and compliance. How Workflows Would Improve the Product Approval Mechanism – When a user submits a request (e.g., access to an application or a provisioning action), it enters a workflow where assigned reviewers must approve or reject it before execution. Role-Based Reviewers – Approval requests could be routed to specific individuals based on their roles (e.g., managers, security officers, or compliance teams). Multi-Step Approvals – Workflows could support multi-tiered approvals where different stakeholders must review a request at various stages. Audit and Compliance – Each approval or rejection would be logged, providing a clear audit trail for governance and regulatory requirements. Example Use Case A user requests access to an HR application. Instead of immediate access, the request follows this workflow: Step 1: The user's manager reviews and approves the request.Step 2: If approved, the HR department reviews and grants final approval.Step 3: Upon approval, the provisioning process assigns the necessary permissions automatically. By incorporating workflows, the product enhances security, ensures compliance, and streamlines access management while preventing unauthorized changes.

To protect NIM configuration natively, we should provide the ability to schedule automatically backups. This is beneficial when there are multiple NIM Administrators making configuration changes and often forget to back up their configuration.

Allow a temporary increase to thresholds in jobs. I have seen several customer NIM environments recently where they had adjusted the job thresholds to allow for the spike in enrollment changes at the beginning of the school year. It was set to really high number and they had forgotten to set it back to a modest number. In one instance, the customer had ALL of their employee's Google groups removed.

Password Reset module of NIM provides a multitude of possibilities but it's prime function is Account recovery via password reset. Previously SSRPM provide a landing page for multiple options (Enroll, Reset Password, Unlock, Manage Attributes, Lookup Username) NIM should provide an option to have a landing page that can provide options for different Password Reset profiles (e.g. Reset Password, Unlock Only). This provides a simple point of entry. Expansion on this is to allow only certain hostnames to be allowed. For example if my nim host name is "nim.domain.com", I maybe want to have password reset point to "reset.domain.com". This would mean then if I go to "reset.domain.com" I would land on the dashboard page to select my option.

It's no fun getting evaluation reports every hour that show zero changes to be made. An option to only send evaluation reports when there are changes to be made in the target systems would be nice.

If Roles could be tagged with a Type, then when scheduled, rather than just selecting groupMembership -> target it could be groupMembership ->target to only run the specific tagged roles for that target. This could allow separation of Role concerns (e.g. Students roles not running Employee roles).

Currently, you have to export all columns that are turned on in a filter. This prevents you from using ordering on data that you don't want in the export. There should be an option to select which columns that are present in the filter that we want to export in the scheduler's export and multi-export options.

Provide the option to attach files to mail templates. Perhaps we can provide the ability to specify an attachment(s) by specifying a path, filter or audit query.