Extending Data Security with Custom Security Contexts

fbarazan-Oracle

Summary: 

Custom Security Contexts help organizations extend Oracle Fusion Data Intelligence security beyond standard options, making it easier to align data access with real business needs. This feature allows teams to apply more precise access rules and reduce unnecessary data exposure. 

Detail: 

Custom Security Contexts in Fusion AI Data Platform give administrators a way to define added security contexts and assign them to data roles, beyond the ready-to-use options that come with the product. Security configurations for data application roles enable defining data security filtering for an application role directly from the Security page. 

This is the way to add extra security assignments for users, in addition to out of the box security context or using Semantic Model Extensions Security Configuration.  

Why does this matter? In real projects, the standard security options do not always match how a business wants to control access. For example, a team may need users to see data by a business-specific attribute that is not available out of the box – like securing General Ledger data by Cost Center when Cost Center is not a ready-to-use security context. 

Another common example is when people with the same functional role should not see the same data. Users can share the same role yet still need

different data security assignments, such as one person seeing one business unit and another person seeing a different one. Custom security contexts extend that idea, so teams can apply more precise access rules where needed, helping keep analysis relevant while reducing overexposure to data. 

 

 

Quick Tips: 

• Make sure the dimension or attribute you want to secure is connected to the fact tables you want protected; Oracle recommends confirming those joins before setting up a custom context. 
• If you expect a high number of filter values, Oracle recommends using the Custom Security Context capability rather than the older Security Configurations approach for better optimization. 
• Keep your naming clear and consistent for roles, groups, and functional groups so future administrators can understand what each security rule is meant to do. 

 

 

Resource Links: 

 

For official guidance, start with Oracle’s documentation, here. 

Define and Assign Custom Security Contexts 

About Data Access through Security Assignments 

Bhaskar Konar

Great explanation of how Custom Security Contexts can extend data security in Fusion AI Data Platform. The practical examples and quick tips make this very helpful for teams looking to implement more precise access controls.

Thanks for sharing, @fbarazan-Oracle!