You are on page 1of 3

CHAPTER 4 Security Part II: Auditing Database Systems shared by all organizational users.

With access
to the full domain of entity data, changes in
The term database is used in a broad context to user information needs can be satisfied without
include two general approaches: the flat-file model and obtaining additional private data sets.
the database model

DATA MANAGEMENT APPROACHES KEY ELEMENTS OF THE DATABASE


ENVIRONMENT
Flat-File Approach - Flat files are data files that contain  Database Management System
records with no structured relationships to other files.  Program development - to create applications
The flat-file approach is most often associated with so- to access the database.
called legacy systems.  Backup and recovery- DBMS can recover to an
earlier version that is known to be correct
The flat-file environment promotes a single-user view
 Database usage reporting- captures statistics on
approach to data management whereby end users own
what data are being used, when they are used,
their data files rather than share them with other users
and who uses them
Data redundancy- replication of essentially the same  Database access- The most important feature of
data in multiple files. It contributes to three significant a DBMS is to permit authorized user access,
problems in the flat-file environment: data storage, both formal and informal, to the database
data updating, and currency of information
Data definition language (DDL) is a
Task-data dependency- user’s inability to obtain programming language used to define the
additional information as his or her needs change database to the DBMS. The DDL identifies the
names and the relationship of all data elements,
Database Approach -This approach centralizes the
records, and files that constitute the database.
organization’s data into a common database that is
This definition has three levels, called views: the
shared by other users. With the enterprise’s data in a
physical internal view, the conceptual view
central location, all users have access to the data they
(schema), and the user view (subschema).
need to achieve their respective objectives. Through
data sharing, the traditional problems associated with
Database Views
the flat-file approach may be overcome.
Internal View/Physical View. This is the lowest
 Elimination of Data Storage Problem - Each level of representation, which is one step
data element is stored only once, thereby removed from the physical database. This
eliminating data redundancy and reducing data internal view describes the structures of data
collection and storage costs records, the linkages between files, and the
 Elimination of Data Update Problem- Because physical arrangement and sequence of records
each data element exists in only one place, it in a file. There is only one internal view for the
requires only a single update procedure. This database.
reduces the time and cost of keeping the Database Views Internal View/Physical View.
database current. The physical arrangement of records in the
 Elimination of Currency Problem- A single database is presented through the internal
change to a database attribute is automatically view. This is the lowest level of representation,
made available to all users of the attribute which is one step removed from the physical
 Elimination of Task-Data Dependency Problem database. This internal view describes the
-The most striking difference between the structures of data records, the linkages
database model and the flat-file model is the between files, and the physical arrangement
pooling of data into a common database that is
and sequence of records in a file. There is only Data Access Methods - is the technique used to
one internal view or the database. locate records and to navigate through the
External View/User View (Subschema). The database
subschema or user view, defines the user’s Data Attribute/Field. A data attribute (or field)
section of the database—the portion that an is a single item of data, such as customer’s
individual user is authorized to access name, account balance, or address
Entity. An entity is a database representation of
 Users an individual resource, event, or agent about
Data manipulation Language(DML) is the which we choose to collect data.
proprietary programming language that a Record Type (Table or File). When we group
particular DBMS uses to retrieve, process, and together the data attributes that logically define
store data. Entire user programs may be written an entity, they form a record type
in the DML or, alternatively, selected DML Navigational Databases. The hierarchical data
commands can be inserted into programs that model is called a navigational data- base
are written in universal languages, such as because traversing the files requires following a
JAVA, C++, and even older languages such as predefined path.
COBOL and FORTRAN. The Network Model - Like the hierarchical
model, the network model is a navigational
A query is an ad hoc access methodology for database with explicit linkages between records
extracting information from a database. Users and files. The distinction is that the network
can access data via direct query, which requires model permits a child record to have multiple
no formal user programs using the DBMS’s parents.
built-in query facility. The Relational Model - The relational model
portrays data in the form of two-dimensional
IBM’s Structured Query Language (SQL) (often tables
pronounced sequel or S-Q-L), has emerged as Partitioned database approach splits the
the standard query language for both central database into segments or partitions
mainframe and microcomputer DBMSs. SQL is a that are distributed to their primary user
fourth-generation, nonprocedural language Deadlock is a permanent condition that must
(English-like commands) with many commands be resolved by special software that analyzes
that allow users to input, retrieve, and modify each deadlock condition to determine the best
data easily solution, can result in transactions being
incompletely processed and the database being
Database administrator (DBA). The DBA is corrupted.
responsible for managing the database Resolving a deadlock usually involves
resource. The sharing of a common database by terminating one or more transactions to
multiple users requires organization, complete processing of the other transactions
coordination, rules, and guidelines to protect in the deadlock.
the integrity of the database. Replicated databases are effective in
companies where there exists a high degree of
Data structures are the bricks and mortar of the data sharing but no primary user
database Database concurrency is the presence of
Data Organization of a file refers to the way complete and accurate data at all user sites
records are physically arranged on the
secondary storage device, this may be either CONTROLLING AND AUDITING DATA
sequential or random MANAGEMENT SYSTEMS
Access controls are designed to prevent Checkpoint facility suspends all data processing
unauthorized individuals from viewing, while the system reconciles the transaction log
retrieving, corrupting, or destroying the entity’s and the database change log against the
data. database.
Backup controls ensure that in the event of Recovery module uses the logs and backup files
data loss due to unauthorized access, to restart the system after a failure.
equipment failure, or physical disaster the
organization can recover its database.
The user view or subschema is a subset of the
total database that defines the user’s data
domain and provides access to the database
Data base authorization table contains rules
that limit the actions a user can take
User-defined procedure allows the user to
create a personal security program or routine to
provide more positive user identification than a
single password

Audit Procedures for Testing Database Access


Controls
 Responsibility for Authority Tables and
Subschemas.
 Appropriate Access Authority
 Biometric Controls.
 Inference Controls.
 Encryption Controls.
 Backup Controls

Audit Procedures for Testing Flat-File Backup


Controls
 Sequential File (GPC) Backup- select a sample
of systems and determine from the system
documentation that the number of GPC backup
files specified for each system is adequate.
 Backup Transaction Files- verify through
physical observation that transaction files used
to reconstruct the master files are also retained
 Direct Access File Backup - should select a
sample of applications and identify the direct
access files being updated in each system
 Off-Site Storage- verify the existence and
adequacy of off-site storage.

Transaction log feature provides an audit trail


of all processed transactions.

You might also like