Information Systems Audit Flashcards
Domain 1 - The process of the Auditing Information Systems
The ISACA Code of Professional Ethics 1
Members and ISACA certification holders shall:
- Support the implementation of, and encourage compliance with, appropriate standards and procedures for the effective governance and management of enterprise information systems and technology, including: audit, control, security and risk management.
The ISACA Code of Professional Ethics 2
Members and ISACA certification holders shall:
- Perform their duties with objectivity, due diligence and professional care, in accordance with professional standards.
The ISACA Code of Professional Ethics 3
Members and ISACA certification holders shall:
- Serve in the interest of stakeholders in a lawful manner, while maintaining high standards of conduct and character, and not discrediting their profession or the Association.
The ISACA Code of Professional Ethics 4
Members and ISACA certification holders shall:
- Maintain the privacy and confidentiality of information obtained in the course of their activities unless disclosure is required by legal authority. Such information shall not be used for personal benefit or released to inappropriate parties.
The ISACA Code of Professional Ethics 5
Members and ISACA certification holders shall:
- Maintain competency in their respective fields and agree to undertake only those activities they can reasonably expect to complete with the necessary skills, knowledge and competence.
The ISACA Code of Professional Ethics 6
Members and ISACA certification holders shall:
- Inform appropriate parties of the results of work performed including the disclosure of all significant facts known to them that, if not disclosed, may distort the reporting of the results.
The ISACA Code of Professional Ethics 7
Members and ISACA certification holders shall:
- Support the professional education of stakeholders in enhancing their understanding of the governance and management of enterprise information systems and technology, including: audit, control, security and risk management.
Standards
Mandatory actions, explicit rules, or controls that are designed to support and conform to a policy. A standard should make a policy more meaningful and effective by including accepted specifications for hardware, software, or behavior. Standards should always point to the policy to which they relate.
Standards articulate what must be followed, and they are typically technology platform agnostic.
Procedures
Written steps to execute policies through specific, prescribed actions; this is the how in relation to a policy. Procedures tend to be more detailed than policies. They identify the method and state, in a series of steps, exactly how to accomplish an intended task, achieve a desired business or functional outcome, and execute a policy.
A procedure usually is a series of steps to achieve a specific outcome—for example, the particular steps in a company that you have to take to obtain a logon account for a new employee.
If the document is purely procedural steps with a focus on a specific outcome (such as a deliverable), you can treat it as a procedure.
Guidelines
An outline for a statement of conduct. This is an additional (optional) document in support of policies, standards, and procedures and provides general guidance on what to do in particular circumstances. Guidelines are not requirements to be met but are strongly recommended.
In comparison, a guideline is more of a use case for a standard. A guideline explains how to comply with a standard. Guidelines are optional, intended to give organizations examples of successful implementation of ISACA standards.
Baselines
Platform-specific rules that are accepted across the industry as providing the most effective approach to a specific implementation.
A baseline is platform specific on a set of accepted rules—for example, setting a workstation’s Windows 10 platform to time out after 15 minutes.
For the ISACA exam, remember that if a document is platform specific to implement a specific rule, you can treat it as a baseline.
Industry Norm
Emerges from the combination of industry guidance documents and regulation guidance
Benefits of Effectively Adopting Industry Guidance
- Demonstrating to customers compliance with industry best practices
- Demonstrating the ability to adopt lessons learned across the globe
- Ensuring that organizations’ products and services meet quality and environmental stewardship
- Proving through audits that an organization’s systems operate according to accepted norms, as defined by industry standards
- Ensuring that products and services are produced with acceptable consistency
- Reacting quickly to emerging events related to technology defects and breaches
Important U.S. Industry Guidance
COBIT
ISO
NIST
FIPS
COBIT
Control Objectives for Information and Related Technologies (COBIT) was first published in 1996 as one of the first definitive guides for IS auditors. COBIT has evolved into a globally accepted framework, providing an end-to-end business view of the governance of enterprise IT. COBIT 5 is the latest version and is considered a framework that embodies global thought guidance for information systems audit, assurance, and control functions.