Back to Oracle Label Security homepage

Oracle Label Security


Successful Multi-level Security implementation

 
Oracle Label Security Multi-level Security step 1 of 6
 
 
 
 
Oracle Label Security Multi-level Security step 2 of 6
 
 
 
 
Oracle Label Security Multi-level Security step 3 of 6
 
 
 
 
Oracle Label Security Multi-level Security step 4 of 6
 
 
 
 
Oracle Label Security Multi-level Security step 5 of 6
 
 
 
 
Oracle Label Security Multi-level Security step 6 of 6
 
Identify tables holding sensitive data Classify your data Examine user population Determine valid labels Create an OLS policy Add labels to existing and new data



Not all permutations of the label components found in step two are used; for example, "Mergers and Aquisitions" are always "Top Secret" and are never decided on a country level, so the Group is "EMEA". The label for this example would be:

  Top Secret:Mergers and Aquisitions:EMEA 


Hands-On


 Using OLS user authorizations to create powerful Command Rules in Oracle Database Vault
 OLS user authorizations in VPD policies: Determine access to application table columns based on user authorizations
 Six steps towards a successful multi level security implementation

Security Features


Strong Authentication
Network Encryption
Real Application Security
Unified Auditing
Secure External Password Store
Virtual Private Database
Traditional Database Auditing
Proxy Authentication
Enterprise User Security
Secure Application Roles
Fine Grained Auditing

Discussion Forums


 Security
 Oracle Audit Vault and Database Firewall
 Database

Technical Information


 Datasheet
 Overview White Paper
 Government and Defense Environments White Paper
 Technical White Paper
 Best Practices
 Frequently Asked Questions
 Oracle Label Security with Oracle E-Business Suite: Best Practices

Security Solutions


 Oracle Database Vault
 Oracle Advanced Security
 Oracle Label Security
Oracle Audit Vault and Database Firewall
Data Masking
Oracle Open World 2014 Banner

In-Memory Replay Banner