10.10.2014 Views

Policy 7230A - Department of Administration

Policy 7230A - Department of Administration

Policy 7230A - Department of Administration

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.

4.3.1.5 Ensure Cryptographic Authentication Meets Standards<br />

Cryptography is a valuable tool in the protection <strong>of</strong> authentication<br />

information. However, to ensure the utmost functionality, selected<br />

tools must meet set standards:<br />

• Where authentication is performed against a cryptographic<br />

module, review the cryptographic module to ensure it meets<br />

FIPS 140-2 standards.<br />

4.3.1.6 Initiate Session Lock and Termination<br />

After a pre-defined period <strong>of</strong> inactivity internally initiated system<br />

sessions must be locked and require re-authentication should further<br />

work in the system be required. Further, after a pre-defined period <strong>of</strong><br />

inactivity externally initiated system sessions must be terminated and<br />

require re-establishing should further work within the system be<br />

required:<br />

• Internally initiated system sessions are those that are initiated<br />

from within the network <strong>of</strong> the host system.<br />

• Externally initiated system sessions are those that are initiated<br />

from outside <strong>of</strong> the network <strong>of</strong> the host system.<br />

• Session lock maintains an active session such that information<br />

in the process <strong>of</strong> being entered is not lost.<br />

• Session termination closes an active session and any<br />

information that is in the process <strong>of</strong> being entered may be<br />

lost.<br />

4.3.2. Configure Systems for Secure Communication<br />

Agencies should limit the potential <strong>of</strong> security threats bridging systems and <strong>of</strong><br />

data leaking inadvertently by restricting inter-system communications:<br />

4.3.2.1 Restrict Intra and Inter-System Communication by Authorization<br />

To ensure that information is not shared inappropriately, intra and<br />

inter-system communications must be fully authorized before being<br />

established:<br />

• Define the specific communication paths and communications<br />

that will occur intra and inter-system.<br />

• Identify system owners for all involved systems and data<br />

owners for all involved data.<br />

• Obtain written sign-<strong>of</strong>f on all communications by system and<br />

data owners per system.<br />

10

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

Saved successfully!

Ooh no, something went wrong!