CPSA ยท Database security
Default Oracle accounts
Well-known default accounts and passwords and how to remove or lock them.
Key points
- SYS: owns the data dictionary, used for SYSDBA connections.
- SYSTEM: DBA account for routine administration. DBSNMP: monitoring agents.
- SCOTT: legacy demo schema, not installed by default in recent releases.
- Well-known names: prime guessing targets, especially with shipped passwords.
- Fix: change default passwords, lock and expire unneeded accounts (ALTER USER <name> ACCOUNT LOCK), check DBA_USERS (status, default passwords).
Practice questions
Which default Oracle account owns the data dictionary?
- SYSTEM
- DBSNMP
- SYS
- SCOTT
Show answer
Answer: C. SYS
SYS owns the data dictionary. SYSTEM is a DBA account for routine administration but not the dictionary owner; DBSNMP is for monitoring; SCOTT is a legacy demo schema.
Which actions help remediate risky default Oracle accounts?
- Change default passwords
- Lock accounts that are not needed
- Share one admin password across all schemas
- Grant DBA to the demo account for convenience
- Check DBA_USERS for account status
Show answer
Answer: A. Change default passwords, B. Lock accounts that are not needed, E. Check DBA_USERS for account status
Changing default passwords and locking unneeded accounts are the core fixes. Sharing passwords or granting more privileges makes things worse.
True or false: because SYS and SYSTEM are the built-in administrators, it is good practice to lock them immediately after installation.
Show answer
Answer: False
False. Locking SYS or SYSTEM without a tested recovery plan can cost you administrative access. The advice is to set strong passwords and limit who uses them, while locking unneeded accounts such as demo or sample users.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
