22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1.3.4 Access control<br />

Access control allows an organization to protect critical resources by limiting<br />

access to only authorized and authenticated users. In other words, access<br />

control is any mechanism by which a system grants or revokes the right to<br />

access some data, or perform some action. Normally, a user must first log in to a<br />

system, using some authentication system. Next, the access control mechanism<br />

controls what operations the user may or may not make by comparing the user<br />

ID to an access control list entry in a database.<br />

Access control systems include a number of permissions and privileges, some of<br />

which are the following:<br />

► File permissions, such as create, read, edit,or delete on a file server<br />

► Program permissions, such as the right to execute a program on an<br />

application server<br />

► Data rights, such as the right to retrieve or update information in a database<br />

► Managerial rights, such as the ability to confer to some users new access<br />

privileges and/or revoke such privileges to some other users<br />

1.3.5 Non-repudiation<br />

Depending on the environment, access may be controlled by the resource<br />

owner, or it may be done automatically by the system through security labels.<br />

The resource owner can specify who can access the information, how it can be<br />

accessed, when it can be accessed, and under what conditions it can be<br />

accessed (for example, when executing specific applications, programs, or<br />

transactions).<br />

The functional goal is to assure that security is maintained for resources, whether<br />

they are in a central system, distributed, or mobile (as is the case with files and<br />

programs).<br />

Non-repudiation can be viewed as an extension to the identification and<br />

authentication services, since non-repudiation relies on authentication to know<br />

who someone is. Obviously, if authentication is weak, then so is the<br />

organization’s ability to know who’s doing what.<br />

The non-repudiation service can protect a recipient against a false denial by an<br />

originator that the data has been sent, and it can protect an originator against the<br />

false denial of a recipient that the data has been received.<br />

Chapter 1. Fundamentals of IT security 21

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!