Computer Audit
Computer Audit
Computer Audit
Computer Audit
Systems can include personal computers, servers, mainframes, network routers,
switches. Applications can include Web Services, Microsoft Project Central,
Oracle Database. (examples only).
Audit Event Reporting
During the last few decades systematic audit record generation (also called audit event
reporting) can only be described as ad hoc. Ironically, in the early days of mainframe and minicomputing with large scale, single-vendor, custom software systems from companies such as
IBM and Hewlett Packard, auditing was considered a mission-critical function. Over the last 30
years, COTS or Commercial Off The Shelf software applications and components, and micro
computers have gradually replaced custom software and hardware as more cost-effective
business management solutions.
During this transition, the critical nature of audit event reporting gradually transformed
into low priority customer requirements.
Software consumers, having little else to fall back on, have simply accepted the lesser
standards as normal. The consumer licenses of existing COTS software disclaim all liability for
security, performance and data integrity issues.
Types of Audit Event Reporting
1. Traditional Logging
Using traditional logging methods, applications and components submit free-form text messages
to system logging facilities such as the Unix Syslog process, or the Microsoft Windows System,
Security or Application event logs.
Java applications often fall back to the standard Java logging facility.
These text messages usually contain information only assumed to be security-relevant by the
application developer, who is often not a computer- or network-security expert.
The fundamental problem with such free-form event records is that each application developer
individually determines what information should be included in an audit event record, and the
overall format in which that record should be presented to the audit log.
This variance in formatting among thousands of instrumented applications makes the job of
parsing audit event records by analysis tools,
Example
Computer Audit
difficult and error prone -such domain and application specific parsing code included in
analysis tools is also difficult to maintain, as changes to event formats inevitably work
their way into newer versions of the applications over time.
2. Modern Auditing Services
Most contemporary enterprise operating systems, including Microsoft Windows, Solaris, Mac
OS X, and FreeBSD (via the TrustedBSD Project) support audit event logging due to
requirements in the Common Criteria (and more historically, the Orange Book).
Both FreeBSD and Mac OS X make use of the open source OpenBSM library and command
suite to generate and process audit records.
The importance of audit event logging has increased with recent new (post-2000) US and
worldwide legislation mandating corporate and enterprise auditing requirements.
Performing an Audit
Generally, computer security audits are performed by:
1. Federal or State Regulators - Certified accountants, CISA. Federal OTS, OCC,
DOJ, etc.
2. Corporate Internal Auditors - Certificated accountants, CISA.
3. Corporate Security Staff - Security managers, CISSP, CISM.
4. IT Staff - subject matter experts, oversight support.
Audit Process
1. Audit planning & preparation
The auditor should be adequately educated about the company and its critical business
activities before conducting a data center review.
The objective of the data center is to align data center activities with the goals of the business
while maintaining the security and integrity of critical information and processes. To adequately
determine if whether or not the clients goal is being achieved, the auditor should perform the
following before conducting the review:
Computer Audit
Research all operating systems, software applications and data center equipment
operating within the data center
Appropriate back up procedures are in place to minimize downtime and prevent loss of
important data
The data center has adequate physical security controls to prevent unauthorized access to
the data center
Adequate environmental controls are in place to ensure equipment is protected from fire
and flooding
Computer Audit
Data center personnel All data center personnel should be authorized to access the data
center (key cards, login IDs, secure passwords, etc.). Data center employees are
adequately educated about data center equipment and properly perform their jobs. Vendor
service personnel are supervised when doing work on data center equipment. The auditor
should observe and interview data center employees to satisfy their objectives.
Equipment The auditor should verify that all data center equipment is working properly
and effectively. Equipment utilization reports, equipment inspection for damage and
functionality, system downtime records and equipment performance measurements all
help the auditor determine the state of data center equipment. Additionally, the auditor
should interview employees to determine if preventative maintenance policies are in
place and performed.
Policies and Procedures All data center policies and procedures should be documented
and located at the data center. Important documented procedures include: data center
personnel job responsibilities, back up policies, security policies, employee termination
policies, system operating procedures and an overview of operating systems.
Physical security / environmental controls The auditor should assess the security of the
clients data center. Physical security includes bodyguards, locked cages, man traps,
single entrances, bolted down equipment, and computer monitoring systems.
Additionally, environmental controls should be in place to ensure the security of data
center equipment. These include: Air conditioning units, raised floors, humidifiers and
uninterruptible power supply.
Backup procedures The auditor should verify that the client has backup procedures in
place in the case of system failure. Clients may maintain a backup data center at a
separate location that allows them to instantaneously continue operations in the instance
of system failure.
Interception: Data that is being transmitted over the network is vulnerable to being
intercepted by an unintended third party who could put the data to harmful use.
Computer Audit
Access/entry point: Networks are vulnerable to unwanted access. A weak point in the
network can make that information available to intruders. It can also provide an entry
point for viruses and Trojan horses.
B. Controls
Availability controls: The best control for this is to have excellent network architecture
and monitoring. The network should have redundant paths between every resource and an
access point and automatic routing to switch the traffic to the available path without loss
of data or time.
Access/entry point controls: Most network controls are put at the point where the network
connects with external network. These controls limit the traffic that pass through the
network. These can include firewalls, intrusion detection systems, and antivirus software.
The auditor should ask certain questions to better understand the network and its vulnerabilities.
The auditor should first assess what the extent of the network is and how it is structured. A
network diagram can assist the auditor in this process. The next question an auditor should ask is
what critical information this network must protect. Things such as enterprise systems, mail
servers, web servers, and host applications accessed by customers are typically areas of focus. It
is also important to know who has access and to what parts.
Questions Commonly Asked?
Do customers and vendors have access to systems on the network?
Can employees access information from home?
Lastly the auditor should assess how the network is connected to external networks and
how it is protected.
Most networks are at least connected to the internet, which could be a point of vulnerability.
These are critical questions in protecting networks.
Computer Audit
Companies with multiple external users, e-commerce applications, and sensitive
customer/employee information should maintain rigid encryption policies aimed at encrypting
the correct data at the appropriate stage in the data collection process.
Auditors should continually evaluate their clients encryption policies and procedures.
Companies that are heavily reliant on e-commerce systems and wireless networks are extremely
vulnerable to the theft and loss of critical information in transmission.
Policies and procedures should be documented and carried out to ensure that all transmitted data
is protected.
The auditor should verify that management has controls in place over the data encryption
management process.
Access to keys should require dual control, keys should be composed of two separate
components and should be maintained on a computer that is not accessible to programmers or
outside users.
Management should attest that encryption policies ensure data protection at the desired level and
verify that the cost of encrypting the data does not exceed the value of the information itself.
All data that is required to be maintained for an extensive amount of time should be encrypted
and transported to a remote location.
Procedures should be in place to guarantee that all encrypted sensitive information arrives at its
location and is stored properly.
Finally the auditor should attain verification from management that the encryption system is
strong, not attackable and compliant with all local and international laws and regulations.
Passwords: Every company should have written policies regarding passwords, and
employees use of them. Passwords should not be shared and employees should have
mandatory scheduled changes. Employees should have user rights that are in line with
their job functions. They should also be aware of proper log on/ log off procedures. Also
helpful are security tokens, small devices that authorized users of computer programs or
networks carry to assist in identity confirmation. They can also store cryptographic keys
and biometric data. The most popular type of security token (RSAs SecurID) displays a
number which changes every minute. Users are authenticated by entering a personal
identification number and the number on the token.
Computer Audit
Special User Accounts: Special User Accounts and other privileged accounts should be
monitored and have proper controls in place.
Remote Access: Remote access is often a point where intruders can enter a system. The
logical security tools used for remote access should be very strict. Remote access should
be logged.