0% found this document useful (0 votes)
46 views37 pages

Database Security and Auditing: Protecting Data Integrity and Accessibility

1. Administration of users is an important part of database security and involves properly documenting, creating, modifying, and removing users. 2. Documentation of user administration policies and procedures provides a paper trail and ensures consistency. It should document administration staff, security policies, and implementation scripts. 3. Creating users involves using tools like SQL statements or graphical interfaces to define authentication methods, storage quotas, and other profile settings for each user. Best practices include having a standardized process and removing or modifying users only with documentation.

Uploaded by

endale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
46 views37 pages

Database Security and Auditing: Protecting Data Integrity and Accessibility

1. Administration of users is an important part of database security and involves properly documenting, creating, modifying, and removing users. 2. Documentation of user administration policies and procedures provides a paper trail and ensures consistency. It should document administration staff, security policies, and implementation scripts. 3. Creating users involves using tools like SQL statements or graphical interfaces to define authentication methods, storage quotas, and other profile settings for each user. Best practices include having a standardized process and removing or modifying users only with documentation.

Uploaded by

endale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 37

Database Security and Auditing:

Protecting Data Integrity and


Accessibility

Chapter 3
Administration of Users
Objectives
• Importance of administration documentation
• Concept of operating system authentication
• User Administration using both Oracle and
SQL Server
• Create and remove users and logins
• Modify an existing user using both Oracle and
SQL servers
• List all default users on Oracle and SQL servers
• Describe best practices for user
administration
2
Documentation of User Administration

• Part of the administration process


• Reasons to document:
• Provide a paper trail
• Ensure administration consistency
• What to document:
• Administration policies, staff and management
• Security procedures
• Procedure implementation scripts or programs
• Predefined roles description

3
Documentation of User Administration
(continued)

4
Documentation of User Administration
(continued)

5
Operating System Authentication

• Many databases (including Microsoft SQL


Server 2000) depend on OS to authenticate
users
• Once an intruder is inside the OS, it is easier
to access the database
• Centralize administration of users
• Ideally, users must be authenticated at each
level

6
Operating System Authentication (continued)

7
Creating Users

• Must be a standardized, well-documented,


and securely managed process
• Several ways in Oracle:
1. CREATE USER Statement from iSQLPlus
2. Oracle Enterprise Manager: GUI administration
tool using database authentication
3. Creating an Oracle User Using External
(Operating System) Authentication
4. SQL developer

8
Creating Users

• In Oracle, use the CREATE USER statement:


• Part of the a Data Definition Language (DDL)
• Account can own different objects

CREATE USER {name}


IDENTIFIED {BY password | EXTERNALLY | GLOBALLY as
‘external_name’}
[DEFAULT TABLESPACE {tbspname}]
[TEMPORARY TABLESPACE {tmpname}]
[QUOTA {integer {K|M} ON {tbspname}]
[PROFILE {pname}]
[PASSWORD EXPIRE]
[ACCOUNT {lock | unlock}]

9
Creating an Oracle User

• IDENTIFIED clause
• Tells Oracle how to authenticate a user account
• BY PASSWORD option: encrypts and stores an
assigned password in the database
• EXTERNALLY option: user is authenticated by
the OS
• GLOBALLY AS option: depends on
authentication through centralized user
management method

10
Creating an Oracle User (continued)

11
Creating an Oracle User (continued)

• DEFAULT TABLESPACE clause: specifies default


storage for the user
• TEMPORARY TABLESPACE clause
• QUOTA clause: tells Oracle DB how much storage
space a user is allowed for a specified tablespace
• PROFILE clause: indicates the profile used for
limiting database resources and enforcing password
policies

12
Example

CREATE USER STUDENTA


IDENTIFIED BY TRUE#1
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
QUOTA 10M ON USERS
QUOTA 5M ON USER_AUTO
PROFILE DEFAULT
ACCOUNT UNLOCK;

13
Creating an Oracle User (continued)

14
Creating an Oracle User (continued)

• PASSWORD EXPIRE clause: tells Oracle to


expire the user password and prompts the
user to enter a new password
• ACCOUNT clause: enable or disable
account
• ALTER USER: modifies a user account
• Oracle Enterprise Manager: GUI
administration tool

15
Creating an Oracle User (continued)

16
Creating an Oracle User (continued)

17
Creating an Oracle User Using External
(Operating System) Authentication

• Depends on an external party to authenticate


the user
• Steps:
• Verify account belongs to ORA_DBA group
• Set the Windows registry string
OSAUTH_PREFIX_DOMAIN to FALSE
• View setting of the OS_AUTHENT_PREFIX
initialization parameter
• Change OS_AUTHENT_PREFIX to NULL

18
Creating an Oracle User Using External
(Operating System) Authentication (continued)
Step 1:The window OS account that you want Oracle 10g to use for external authentication
must belong to the ORA_DBA group. Go to Control Panel  Administrative Tools 
Computer Management Tool to verify. You can use one of OS accounts.

19
Creating an Oracle User Using External (Operating
System) Authentication (continued)
Step 2: You must set the windows registry string OSAUTH_PREFIX-
DOMAIN to false. Use “regedit” from run, and navigate to
HKEY_LOCAL_MACHINE, SOFTWARE, ORACLE, HOME1 (or 2).
Create one if the parameter does not exist.

20
Creating an Oracle User Using External (Operating
System) Authentication (continued)
Step 3: SQL> SHOW PARAMETER PREFIX
Change the OS_AUTHENT_PREFIX initialization parameter value to
NULL.

Step 4: Create an Oracle user with the same name as the windows user name
that is used for external authentication.

SQL> CREATE USER user_name IDENTIFIED EXTERNALLY


2/
User created.

21
Creating an Oracle User Using External (Operating
System) Authentication (continued)

Step 5: Provide new user with CREATE SESSION privilege

SQL>GRANT CREATE SESSION TO EXTERNAL_USER;


Grant succeeded.
Step 6: Log off the Oracle SYS or SYSTEM account and windows account.
Step 7: log in again using user_name.
Step 8: From command line type sqlplus

• Advantage: allows administrators to use one


generic user to run maintenance scripts
without a password

22
More on Password

• Even DBA can not recover real value of password


from the database
• You can change the password and inform the user of
the new password
• You make the password expire immediately so the
user must choose a new password that he finds
easier to remember.

ALTER USER STUDENTA


IDENTIFIED BY STUDENTA
PASSWORD EXPIRE;

23
Removing Users

• Simple process
• Make a backup first
• Obtain a written request (for auditing
purposes)

24
Removing an Oracle User

• DROP command
• CASCADE option: when user owns database
objects
DROP USER MELVIN CASCADE;
• Recommendations:
• Backup the account for one to three months
• Listing all owned objects
• Lock the account or revoke the CREATE
SESSION privilege

25
Modifying Users

• Modifications involve:
• Changing passwords
• Locking an account
• Increasing a storage quota
• ALTER USER DDL statement

26
Modifying an Oracle User

• ALTER USER statement


• Oracle Enterprise Manager: graphical tool

27
Modifying an Oracle User (continued)

28
Default Users

• Oracle default users:


• SYS, owner of the data dictionary
• SYSTEM, performs almost all database tasks
• ORAPWD, creates a password file
• SQL Server default users:
• SA, system administrator
• BUILT_IN\Administrators

29
Practices for Administrators and
Managers
• Manage:
• Accounts
• Data files
• Memory
• Administrative tasks:
• Backup
• Recovery
• Performance tuning

30
Best Practices

• Follow company’s policies and procedures


• Always document and create logs
• Educate users
• Keep abreast of database and security
technology
• Review and modify procedures

31
Best Practices (continued)

• Block direct access to database tables


• Limit and restrict access to the server
• Use strong passwords
• Patches, patches, patches

32
Quick quiz
• These are the top three excuses for failing to incorporate
documentation as part of the administration process:
• _______________________
• Belief that the administration process is already documented in
the system
• Reluctance to complicate a process that is simple

• The _____________________ is the gateway to the database.

• The _____________________________ clause tells


Oracle11g/12c how to authenticate a user account.
a. PASSWORD EXPIRE
b. IDENTIFIED
c. ACCOUNT
d. QUOTA

33
Quick Quiz

• SQL provides a command called


_________________________ that removes a user
account from the database

• When a user logs on to the database through the


machine where the database is located, the
database is called a ____________________.
a. local database
b. remote database
c. fixed database
d. database server

34
Key Terms

• ACCOUNT UNLOCK is an Oracle option that indicates that an


account is enabled.
• CREATE USER statement is a SQL statement that enables
database administrators to create a database user account.
• ODBC (Open Database Connectivity ) is a Microsoft protocol
used for connecting Windows applications to different database
systems, including other SQL servers and Oracle10g servers
• OLEDB (Object Linking and Embedding Database ) is a
Microsoft component that allows Windows applications to
connect and access different database systems.
• Operating system is the gateway to database access.
• Windows authentication is the only type of authentication the
default installation of Microsoft SQL Server 2000 supports.

35
User administration guidelines web sites

• http://www.orafaq.com/faqdba.htm
• http://msdn.microsoft.com/archive/default.asp?url=/
archive/en-us/dnarsql7/html/deploybus_appc.asp
• http://www.cadam.com/whitepapers/db_security.htm
• http://www.oracle.com/technology/documentation/id
s_arch.html
• https://aurora.vcu.edu/db2help/db2d0/frm3toc.htm

36
Labs

• Create a database user account:


• SQL statement
• GUI in Enterprise Manager
• A user authenticated by windows OS.
• Modify a user
• Drop a user

37

You might also like