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

Most likely only a small number of tables hold information that requires labeling. Prime candidates are tables holding "Personally Identifiable Information" (PII), trade secrets, research results, any kind of financial information. Or, after a consolidation project, where physically separated information silos have been put into one database, labeling would maintain the same level of security as if they were still separated, but controlled information exchange between them is now much easier.

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