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.

3. Systems must be able to log invalid access attempts against the access<br />

control policies defined and approved for the system (in other words, define<br />

what constitutes a log exception). The log should contain all information that<br />

would be pertinent to a security investigation such as: user ID, source<br />

address, destination address, time, date, protocol, port, process, and NETID.<br />

4. Systems must have a process for detecting systematic attacks, or detecting<br />

intrusions against the system. Activity logs are instrumental for this purpose,<br />

but should not be the sole method of intrusion detection. If no dedicated<br />

intrusion detection tool is compatible with a given system, then a procedure<br />

must be implemented whereby logs for the system are reviewed regularly and<br />

frequently, such as weekly at a minimum.<br />

5. The organization’s security policy should define procedures for reporting<br />

incidents related to systems and components. It should <strong>cover</strong> incidents that<br />

originate from both external and internal sources. Due to increasing<br />

legislation, the procedures for handling and preserving potential evidence<br />

should be defined as part of the organization’s incident response plan.<br />

Assessment<br />

The assessment function includes health checking, vulnerability scanning and<br />

technical testing. Assessments are the processes and procedures, defined in the<br />

organization’s security policy, whereby the organization has the ability to validate<br />

that the security system components are functioning as designed and as a whole<br />

are providing the protection intended. Periodic assessments are also valuable<br />

because they provide an opportunity to evaluate if the current layers of defense<br />

address the latest potential exploits.<br />

When changes are made that affect the security controls implemented within a<br />

system or subsystem, testing must be completed to assure that the controls<br />

specified are active and continuing to function as designed. Documentation of<br />

changes to any component must be maintained and regularly reviewed to ensure<br />

no security measure has been affected. A formal annual security assessment<br />

review is a recommended best practice. If a security assessment reveals a<br />

negative finding, there should be a procedure defined in the organization’s<br />

security policy that describes the actions required and time frame in which they<br />

must be performed.<br />

The most thorough security assessment will engage a test team to inspect the<br />

overall system. Often, a more thorough and objective assessment will be<br />

conducted if people outside the organization are performing the testing. We<br />

recommend that the results of such a test team investigation be incorporated and<br />

documented as part of the annual security assessment process. We strongly<br />

recommend that the appropriate levels of management approval be obtained<br />

prior to conducting any form of vulnerability testing, and all parties that either<br />

support or use a particular system should be identified as the first step in<br />

Chapter 3. Secure infrastructure requirements 113

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

Saved successfully!

Ooh no, something went wrong!