Oracle Label Security

Successful Multi-level Security implementation

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

Oracle Label Security provides three components for Labels:

• Level (at least one): Determines the sensitivity level of data rows or the clearance level of users. Examples are: "Public", "Internal", "Secret", "Top Secret".
• Compartment (optional; determines 'need-to-know'): Allows compartmentalization of levels; non-hierarchical; users need to have at least all compartments of the data row in order to get access to it; examples are: "Marketing", "Finance", "HR", "Mergers and Aquisitions".
• Group (optional; determines data ownership): Hierarchical; users need to have at least one of the groups of the data row in order to gain access. Example: "EMEA" is the parent group of the groups "Italy", "France", and "Germany".

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 Oracle Magazine: Now Securing Every Row Related Technologies Database Firewall Audit Vault Data Masking (pdf) Secure Backup Configuration Management Identity Management Discussion Forums Security Audit Vault Database

Technical Information Datasheet Overview Whitepaper Oracle Label Security in Government and Defense Environments Technical White Paper Best practices Frequently Asked Questions Oracle Label Security with Oracle E-Business Suite: Best Practices Security Options Oracle Database Vault Oracle Advanced Security Oracle Label Security Security Features Data Encryption Virtual Private Database Database Auditing Backup Encryption Export file encryption Proxy Authentication Enterprise User Security Secure Application Roles Fine Grained Auditing