UNIT-II Reference

Oracle 10g Database
Administrator: Implementation
and Administration
Chapter 12
Security Management
Objectives
• Create, modify, and remove users
• Discover when and how to create, use, and drop
profiles
• Manage passwords
• View information about users, profiles, passwords,
and resources
Oracle 10g Database Administrator: Implementation and Administration 2

Objectives (continued)
• Identify and manage system and object privileges
• Grant and revoke privileges to users
• Understand auditing capabilities and practice using
auditing commands
• Discover when and why to use roles

Objectives (continued)
• Learn how to create, modify, and remove roles
• Learn how to assign roles
• Examine data dictionary views of roles
• Assign roles and privileges using the Enterprise
Management console

Users and Resource Control
• With a new DB instance, two users are created:
– SYS
• Owns most of tables needed to run DB, and data
dictionary views
• Owns a host of packages and procedures built into DB
• Can perform high-level tasks (e.g., starting up and
shutting down DB instance), and backup/recovery tasks
– Do not log on as SYS for routine tasks
– SYSTEM
• Owns some tables, packages, and procedures
• Has the DBA role: it can perform routine DB
administration tasks
– Log on as SYSTEM to perform these routine tasks
Users and Resource Control
(continued)
• During DB creation, Oracle creates other users to
help it install some DB features
– E.g., MDSYS owns objects related to Oracle Spatial
– After DB creation, these users are disabled to prevent
anyone from logging to DB with their accounts
• After the DB instance is up and running, you create
users that own tables and other objects
– So system and user tables are in distinct logical
groups
– You can limit the ability of each user to create objects
• You can create a profile, and assign it to any user
• After creating users to own the business tables, you
must create users who access these tables
Creating New Users

Creating New Users (continued)
GRANT CREATE SESSION TO STUDENTA, STUDENTB;

Modifying User Settings with the
ALTER USER Statement

ALTER USER Statement (continued)

ALTER USER Statement (continued)
ALTER USER STUDENTA
QUOTA UNLIMITED ON USER_AUTO;
ALTER USER STUDENTA
QUOTA 0 ON USERS;

Removing Users
• Removing users requires the DROP USER system
privilege, which the SYSTEM user has.
DROP USER <user> CASCADE;
– Use CASCADE if user owns tables or DB objects
• If a user has created other users, those users are
not dropped when the creating user is dropped
– The new users do not belong to the original user’s
schema
• If a user has created tables you want to keep, do
not drop the user
– Instead, change the user account to LOCK status
Removing Users (continued)

Introduction to Profiles
• Specify a profile when you create/alter a DB user
• Profile: collection of settings that limits the use of
system resources and the database
– A profile can be assigned to any number of users
• A user can be assigned only one profile at a time
– A newly assigned profile overrides the old one
» User’s current session isn’t affected by profile
change
– DEFAULT profile has no resource or DB use limits
• As a system grows, resources may become stretched
– Profiles can be used for managing passwords too
Creating Profiles
CREATE PROFILE <profile> LIMIT
<password_setting> ...
<resource_setting> <limit> ...;
– Password settings:
• FAILED_LOGIN_ATTEMPTS, PASSWORD_LIFE_TIME,
PASSWORD_REUSE_TIME, PASSWORD_REUSE_MAX,
PASSWORD_LOCK_TIME, FAILED_LOGIN_ATTEMPTS,
PASSWORD_GRACE_TIME,
PASSWORD_VERIFY_FUNCTION
– You can limit nine resources:
• SESSSIONS_PER_USER, CPU_PER_SESSION,
CPU_PER_CALL, CONNECT_TIME, IDLE_TIME,
LOGICAL_READS_PER_SESSION,
LOGICAL_READS_PER_CALL, PRIVATE_SGA,
COMPOSITE_LIMIT
Creating Profiles (continued)
• Examples:
CREATE PROFILE PROGRAMMER LIMIT
SESSIONS_PER_USER 2;
CREATE PROFILE POWERUSER LIMIT

PASSWORD_LIFE_TIME 60;

Managing Passwords
• There are three different areas to examine when
working with passwords:
– Changing a password and making it expire
– Enforcing password time limits, history, and other
settings
– Enforcing password complexity
• Uses a combination of a function and a profile
– Predefined SQL script to verify the complexity of a
password
– Adjust the PASSWORD_VERIFY_FUNCTION
setting in a profile and assign that profile to a user

Managing Passwords (continued)





Controlling Resource Usage
• ALTER PROFILE, with resource clauses listed:
ALTER PROFILE <profile> LIMIT
<password_setting> ...
SESSIONS_PER_USER <concurrent sessions>
CPU_PER_SESSION <hundredths of seconds>
CPU_PER_CALL <hundredths of seconds>
CONNECT_TIME <minutes>
IDLE_TIME <minutes>
LOGICAL_READS_PER_SESSION <data blocks>
LOGICAL_READS_PER_CALL <data blocks>
PRIVATE_SGA <bytes>
COMPOSITE_LIMIT <service units>
• Example:
ALTER SYSTEM SET RESOURCE_LIMIT=TRUE;
ALTER PROFILE PROGRAMMER LIMIT
IDLE_TIME 15
CPU_PER_CALL 100;
ALTER RESOURCE COST
CPU_PER_SESSION 1000
PRIVATE_SGA 1;
Controlling Resource Usage
(continued)

Dropping a Profile
• The syntax of DROP PROFILE is similar to the
syntax for dropping a user in that it includes a
CASCADE parameter:
DROP PROFILE <profile> CASCADE;
• You must add CASCADE if any users have been

assigned the profile being dropped
– Oracle automatically resets these users to the
DEFAULT profile
• For example, if three users have been assigned to
the ACCT_MGR profile, drop the profile like this:
DROP PROFILE ACCT_MGR CASCADE;

Obtaining User, Profile, Password, and
Resource Data
• You have already seen the following data
dictionary views while going through the chapter:
– DBA_USERS
• View user profile, password expiration date, and
account status
– DBA_TS_QUOTAS
• View the storage quotas of each user
– RESOURCE_COST
• View the weight setting for each resource used in
calculating COMPOSITE_COST
– DBA_PROFILES
• View the settings for each profile
Resource Data (continued)









System and Object Privileges
• After a user has been created, the user must be
assigned the ability to log on to the database
– Once logged on, the user cannot perform any other
tasks unless given the privilege to do so
• It is possible to give a privilege to all users
• Most privileges are given to specific users or roles
– Role: named group of privileges that can be
assigned to a user as a set rather than individually
• Two types of privileges:
– System privileges
– Object privileges
Identifying System Privileges
• SYSTEM has privileges needed for DBA activities
• There are over 100 system privileges; for example:
– SYSDBA
– SYSOPER
– CREATE SESSION
– CREATE TABLE and CREATE VIEW
– CREATE USER
– CREATE ANY TABLE
– DROP ANY TABLE
– SELECT ANY TABLE
– GRANT ANY [OBJECT] PRIVILEGE
– BACKUP ANY TABLE
Using Object Privileges

Managing System and Object
Privileges
• When you grant a privilege, you assign a privilege
to a user or a role, whether it is a system privilege
or an object privilege
• When you revoke a privilege, you take away the
privilege
• Granting privileges to roles is covered later in this
chapter

Granting and Revoking System
Privileges
• The basic syntax of the GRANT command for
system privileges is:
GRANT <systempriv>, <systempriv>,...|ALL PRIVILEGES
TO <user>,<user>...|PUBLIC
WITH ADMIN OPTION;
• Revoking a system privilege is simple:

REVOKE <systempriv>, <systempriv>,...|ALL PRIVILEGES
FROM <user>, <user>,...|PUBLIC;

Privileges (continued)





Granting and Revoking Object
Privileges
• The syntax for granting object privileges looks like
this:
GRANT <objectpriv>, <objectpriv>,...|ALL

(<colname>,...) ON <schema>.<object>
TO <user>,...|PUBLIC
WITH GRANT OPTION
WITH HIERARCHY OPTION;







Description of Auditing Capabilities
• Monitoring activity in a database is called auditing
– Three types can be run by Oracle 10g automatically:
• Statement auditing: AUDIT UPDATE TABLE BY JACK;
• Privilege auditing: AUDIT CREATE TABLE;
• Object auditing: AUDIT SELECT ON EE_PRIVATE;
• Auditing commands have no effect until you set the
AUDIT_TRAIL initialization parameter
– Modify the init.ora file or the spfile
– Valid settings for AUDIT_TRAIL: TRUE or DB,
FALSE or NONE, OS

(continued)
• Syntax of AUDIT command for object auditing:
AUDIT <objpriv>,<objpriv>,...|ALL
ON <schema>.<object>|DEFAULT|NOT EXISTS
BY SESSION|BY ACCESS
WHENEVER SUCCESSFUL|WHENEVER NOT SUCCESSFUL;
• AUDIT syntax for auditing privileges:

AUDIT <priv>,<priv>,...|ALL PRIVILEGES|CONNECT|RESOURCE|DBA
BY <username>
• The syntax for auditing SQL statements is:

AUDIT <sql>,<sql>...|ALL
BY <username>

(continued)

(continued)

(continued)

(continued)

(continued)
• Data dictionary views you can query for audit trail
results:
– DBA_AUDIT_EXISTS
– DBA_AUDIT_OBJECT
– DBA_AUDIT_SESSION
– DBA_AUDIT_STATEMENT
– DBA_AUDIT_TRAIL
• The above metadata views have a corresponding
USER_counterpart, except DBA_AUDIT_EXISTS

(continued)
• You may want to turn off auditing or change what
you are auditing
– This is done with the NOAUDIT command
• Its structure is exactly like the AUDIT command; it
turns off the auditing it names
• Example:
NOAUDIT SELECT TABLE BY STUDENTB;

NOAUDIT SELECT, UPDATE ON CLASSMATE.EMPLOYEE;

Database Roles
• A role is a collection of privileges that is named and
assigned to users or even to another role
• A role can help you simplify database maintenance
by giving you an easy way to assign a set of
privileges to new users

How to Use Roles

How to Use Roles (continued)

Using Predefined Roles

Using Predefined Roles (continued)

Creating and Modifying Roles
• To create a role:
CREATE ROLE <name>
NOT IDENTIFIED|IDENTIFIED BY <password>
• To assign privileges to a role:

GRANT <privilege> TO <role>;
• To assign the role to a user:

GRANT <role> TO <user>|<role>
WITH ADMIN OPTION;
• The only part of a role you can change is whether it

uses a password:
ALTER ROLE <name>
NOT IDENTIFIED|IDENTIFIED BY <password>
ALTER ROLE UPDATEALL

IDENTIFIED BY U67DATR;

Creating and Assigning Privileges to a
Role
• Example:
CREATE ROLE SELALL;
GRANT SELECT ON CLASSMATE.CLASSIFIED_AD TO SELALL;

GRANT SELECT ON CLASSMATE.CLASSIFIED_SECTION TO SELALL;
GRANT SELECT ON CLASSMATE.CUSTOMER TO SELALL;
GRANT SELECT ON CLASSMATE.CUSTOMER_ADDRESS TO SELALL;
GRANT SELECT ON CLASSMATE.NEWS_ARTICLE TO SELALL;
GRANT SELECT ON CLASSMATE.EMPLOYEE TO SELALL;

Assigning Roles to Users and to Other
Roles

Roles (continued)

Roles (continued)

Limiting Availability and Removing
Roles
• You can control when a role becomes enabled for
a user in these ways:
– Default roles: Creator or the DBA can adjust roles for
a user using ALTER USER
ALTER USER <username> DEFAULT ROLE
<role>,...|ALL|ALL EXCEPT <role>,...|NONE
– Enable roles: User role can enable or disable his role

with the SET ROLE command
SET ROLE
<role> IDENTIFIED BY <password>,...|ALL|ALL EXCEPT|NONE|
– Drop roles: DBA can drop the role from the DB and
thereby cancel the role for all users who had it
DROP ROLE <role>

Roles (continued)

Roles (continued)

Roles (continued)

Data Dictionary Information About
Roles

Roles in the Enterprise Manager
Console

Console (continued)

Console (continued)

Console (continued)

Console (continued)

Console (continued)

Console (continued)

Console (continued)

Summary
• Users are created to either own a schema or access
another user’s schema
• Users identified externally or globally are validated
outside the database
• Tablespace quotas limit a user’s storage space
• Profiles store password and resource limits
– Passwords can be changed by DBA and by user
– Limits include how long a password can stay the same
and when it can be reused
• Can limit CPU usage, connect time, and more

Summary (continued)
• System privileges allow user to manage some part of
the database system
– E.g., SYSDBA and SYSOPER allow user to start up
and shut down the DB, and high-level tasks
– A grant made to PUBLIC gives all users the privilege
– Revoked privileges do not cascade to other users
• Object privileges allow a user to work with an object
– Revoked object privileges cascade to other users
– Object privileges can be granted on columns
– Table owner can grant object privileges on that table
• Grantor grants privilege and grantee receives privilege
– Querying an object without privileges to query causes
an error stating that the object does not exist
Summary (continued)
• Auditing types:
– Statement: activity monitoring on a type of statement
– Privilege: audits commands authorized by privilege
– Object: generates audit trail records on object use
– A group of data dictionary views shows audit trail
records for each type of auditing
• Roles simplify security administration
– Can be granted other roles and privileges
– Predefined roles help speed up administration
– Roles with passwords add security to the roles
– Default roles are roles enabled when you log on
– Dropped roles are revoked from users and other roles

UNIT-II Reference

Uploaded by

Copyright:

Available Formats

UNIT-II Reference

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UNIT-II Reference

Uploaded by

Copyright:

Available Formats

Oracle 10g Database

Oracle 10g Database Administrator: Implementation and Administration 2

Oracle 10g Database Administrator: Implementation and Administration 3

Oracle 10g Database Administrator: Implementation and Administration 4

Oracle 10g Database Administrator: Implementation and Administration 7

GRANT CREATE SESSION TO STUDENTA, STUDENTB;

Oracle 10g Database Administrator: Implementation and Administration 9

Oracle 10g Database Administrator: Implementation and Administration 10

Oracle 10g Database Administrator: Implementation and Administration 11

Oracle 10g Database Administrator: Implementation and Administration 13

CREATE PROFILE POWERUSER LIMIT

Oracle 10g Database Administrator: Implementation and Administration 16

Oracle 10g Database Administrator: Implementation and Administration 17

Oracle 10g Database Administrator: Implementation and Administration 18

Oracle 10g Database Administrator: Implementation and Administration 19

Oracle 10g Database Administrator: Implementation and Administration 20

Oracle 10g Database Administrator: Implementation and Administration 21

Oracle 10g Database Administrator: Implementation and Administration 22

Oracle 10g Database Administrator: Implementation and Administration 24

• You must add CASCADE if any users have been

Oracle 10g Database Administrator: Implementation and Administration 25

Oracle 10g Database Administrator: Implementation and Administration 27

Oracle 10g Database Administrator: Implementation and Administration 28

Oracle 10g Database Administrator: Implementation and Administration 29

Oracle 10g Database Administrator: Implementation and Administration 30

Oracle 10g Database Administrator: Implementation and Administration 31

Oracle 10g Database Administrator: Implementation and Administration 32

Oracle 10g Database Administrator: Implementation and Administration 33

Oracle 10g Database Administrator: Implementation and Administration 34

Oracle 10g Database Administrator: Implementation and Administration 35

Oracle 10g Database Administrator: Implementation and Administration 38

Oracle 10g Database Administrator: Implementation and Administration 39

• Revoking a system privilege is simple:

Oracle 10g Database Administrator: Implementation and Administration 40

Oracle 10g Database Administrator: Implementation and Administration 41

Oracle 10g Database Administrator: Implementation and Administration 42

Oracle 10g Database Administrator: Implementation and Administration 43

Oracle 10g Database Administrator: Implementation and Administration 44

Oracle 10g Database Administrator: Implementation and Administration 45

GRANT <objectpriv>, <objectpriv>,...|ALL

Oracle 10g Database Administrator: Implementation and Administration 46

Oracle 10g Database Administrator: Implementation and Administration 47

Oracle 10g Database Administrator: Implementation and Administration 48

Oracle 10g Database Administrator: Implementation and Administration 49

Oracle 10g Database Administrator: Implementation and Administration 50

Oracle 10g Database Administrator: Implementation and Administration 51

Oracle 10g Database Administrator: Implementation and Administration 52

Oracle 10g Database Administrator: Implementation and Administration 53

• AUDIT syntax for auditing privileges:

• The syntax for auditing SQL statements is:

Oracle 10g Database Administrator: Implementation and Administration 54

Oracle 10g Database Administrator: Implementation and Administration 55

Oracle 10g Database Administrator: Implementation and Administration 56

Oracle 10g Database Administrator: Implementation and Administration 57

Oracle 10g Database Administrator: Implementation and Administration 58

Oracle 10g Database Administrator: Implementation and Administration 59

NOAUDIT SELECT TABLE BY STUDENTB;

Oracle 10g Database Administrator: Implementation and Administration 60

Oracle 10g Database Administrator: Implementation and Administration 61