Privilege Security Management (PriSM)
The essential solution for improving the security of your confidential information in OpenText™ Content Server
Ensuring a more secure and structured OpenText Content Server environment
Keeping control of the content within your Content Server environment is vital. When creating, moving or copying content, you never want sensitive or confidential information exposed. Content Server does not readily provide users with the ability to see what access rights they are giving to the information they publish. As such, they tend to just add content assuming that someone has previously set up permissions correctly on the parent folder. With Privilege Security Management (PriSM), users no longer have to make these unsafe assumptions, giving them the confidence that information they add will be secure and only accessible by the appropriate audience.
Improved taxonomy adherence
Your organization’s taxonomy might look fine on paper, but the standard Content Server access controls do not enforce adherence to its structure. PriSM provides the ability to control where content is added, ensuring that designed file plans are adhered to.
The global nature of access management within a standard Content Server environment can limit the ability of your organization to maintain a structured file plan. Through PriSM you can bring order to your taxonomy, allowing specified users to add only certain types of content into pre-determined locations – a level of control that is not possible in Content Server out-of-the-box.
In addition, PriSM helps you to remove confusion for your less experienced and occasional users. By showing, within the Content Server interface, only those types of content that are permitted to be added, the result is cleaner, easier to use and less confusing.
Reduced risk of publishing confidential material
When documents are moved or copied around Content Server, it is not obvious what access rights will be given to the document in its new location. PriSM surfaces these new rights to the user at the moment of creation. The user can then decide if these are correct and make adjustments accordingly. This avoids assuming content has the correct access rights and makes controlling permissions a part of normal Content Server activities.
How does PriSM work?
- It visually illustrates the access permissions that will be applied to an item when it is created, copied, or moved. This gives you the opportunity to confirm and modify these according to your needs, thus avoiding unintentional exposure of confidential information.
- It limits the kinds of objects that can be created in defined areas of your Content Server repository.
- It adds a finer level of granularity to access permissions than is typically available in Content Server.
- PriSM’s extensions to Content Server privileges are implemented at the API level, ensuring enforcement of governance regardless of how users or processes interact with the environment.
- Provides governance over where specific object types can be created. Specific object types can be disallowed in all instances of a particular volume type. This governance is reflected in whichever interface is being used to reduce confusion.
- Because the applicable permissions are surfaced to the user when adding, moving, or copying content, he/she will know how secure the document will be in the new folder.
- During the same move/copy/create action the user can easily impose stricter access controls for sensitive material.