3. Many audit departments spend their existence in
adversarial relationships with the rest of the
company.
Reporting issues accomplishes nothing, except to
make people look bad, get them fired, and create
hatred of auditors.
The real value comes when issues are addressed
and problems are solved.
Audit Department Issues
4. The real mission of the internal audit
department is to help improve the state of
internal controls. This is accomplished by
performing audits and reporting the results, but
these acts provide no value in and of themselves.
They provide value only when the internal
control issues are resolved.
Requires a shift in focus from “reporting” to
“improving.”
Audit Department Issues
5. To provide independent assurance to the audit
committee (and senior management) that
internal controls are in place at the company and
are functioning effectively.
To improve the state of internal controls at the
company by promoting internal controls and by
helping the company identify control
weaknesses and develop cost-effective solutions
for addressing those weaknesses.
Audit Department Mission
6. Webster : “not influenced or controlled by
others”
Auditors work in the same building as their
fellow employees forming relationships outside
the audit department.
Success of company is of prime interest to the
auditors.
Audit departments include people who have
joined the department from other areas in the
company or plan to rotate out of the audit
department.
Auditor’s relationship with the board of
directors: Bury issues and believe that he will be
allowed to “do the right thing”.
Independence: The Great
Myth
8. Unfortunately, many auditors refuse to provide
guidance and input to teams that are developing
new systems or processes.
Auditors can’t provide input on the controls
within the system because if they do so they’ll no
longer be independent. They say, “How can you
audit something if you’ve already signed off on
the controls?”
The auditor shouldn’t be afraid to brainstorm
about the controls with the team. However, this
should not include actually executing the control,
writing the code for implementing it, or
configuring the system.
Auditor should provide as much input as
Consulting and Early Involvement
(utter nonsense)
9. • Early involvement
• Informal audits
• Knowledge sharing
• Self-assessments
Four Methods for Consulting
10. Once you’ve created a system, tested it, and
implemented it, it is much more expensive to go
back and change it than if you had done it right
the first time.
Ask to be part of the sign-off group
There is the possibility that you will make a
mistake and sign off on the project; even though
the system has internal control weaknesses, but
that’s a chance you have to take.
You should not indicate that internal controls are
not applicable to the system and refuse to
participate; instead, you can provide some high-
level guidance and be done with the project for
Early involvement
11. You’ll likely never go to the audit committee and
report that one of the top fifteen risks that you
need to review for the year is a tiny data center
in a remote location supporting a small handful
of people performing a less-than-critical business
process.
Does this mean that you should never
understand the risks at that site?
The informal audit is the mechanism to use.
Remove the constraints of documenting their
work in detailed work papers. Forget about
taking large representative samples. Let the
auditors act as consultants.
Auditors are able to accomplish in a short time
Informal Audits
12. 1.Audit department agrees on timing and scope of
the informal review with the people who are to
be audited.
2.Auditor creates a checklist of areas that needs
review.
3.The auditor executes those steps, keeping notes
as needed but not creating work papers for
review.
4.At the end, auditor compiles all concerns from
review.
5.Conduct a debriefing meeting with people
audited to discuss issues, their seriousness, and
fixing issues.
Informal Audits - basic steps
13. As an internal auditor, you have a unique blend
of knowledge of the company and expertise in
internal controls. You must be creative in finding
new ways to share knowledge with the rest of
the company.
Audit department should have its own website.
Posting control guidelines on your website
empowers groups expecting an audit.
Posting Common Issues, Best Practices, and
Innovative Solutions.
Post info about audit tools (vulnerability
scanning etc.) that you use in audits, this enables
groups to self assess their controls.
Knowledge Sharing
14. University of Pennsylvania
By failing to prepare, you are preparing to fail -
BEN FRANKLIN
Office of internal audit
http://www.upenn.edu/oacp/audit/index.html
Details of internal control
https://oacp.upenn.edu/audit/audit101/internal-controls-
guidance
/
SBP:
Guidelines on Internal Controls
(Confidential document)
Examples
18. Facilitating an organization in assessing itself.
Known as control self-assessment (CSA) model.
This could be as simple as walking through your
control guidelines.
Self-Assessments
19. An effective internal audit department considers
the audit to be a partnership with fellow
employees and not a policing function.
Following are some basic steps that you can take
to start the journey:
Be intentional about regular updates and meetings
with IT management.
Establish audit liaisons with different IT
organizations.
Get yourself invited to key meetings.
Cultivate an attitude of collaboration and
cooperation.
Implement job swaps with the IT organization.
Relationship Building: Partnering vs.
Policing
20. • Application auditors
• Data extraction and analysis specialists
• IT auditors
The Role of the IT Audit Team
21. Data center facilities This, quite simply, is the
physical building and data center housing the
computer equipment on which the system in
question resides.
Networks This allows other systems and users to
communicate with the system in question when
they do not have physical access to it. This layer
includes basic networking devices such as
firewalls, switches, and routers.
System platform This provides the basic
operating environment on which the higher level
application runs. Examples are operating
systems such as
Potential auditing subject areas
22. Databases This tool organizes and provides
access to the data being run by the end
application.
Applications This is the end application, which
actually is seen and accessed by the end user.
This could be an enterprise resource planning
(ERP) application providing basic business
functions, an e-mail application, or a system that
allows conference rooms to be scheduled.
23. Focus almost solely on the application layer.
Ensuring that access is properly controlled and
that segregation of duties issues do not exist.
Ensuring unauthorized application changes can’t
occur.
Ensuring controls are in place to ensure the
integrity of data.
Application Auditors
24. Experts of data extraction and analysis tools,
such as Audit Command Language (ACL).
Developing analytics that allow for continuous
monitoring for evidence of fraud, internal
control violations, policy noncompliance, and
other abuses.
This tutorial teaches you how to use audit
command language (ACL) to detect ghost names
in payroll.
https://www.youtube.com/watch?v=FObE7i9GsDI
Data Extraction & Analysis Specialists
25. The third model (IT auditors) is critical for
performing thorough and effective IT auditing
because it ensures that all layers are being
covered and that they are being covered by the
people with the highest level of subject matter
knowledge.
IT Auditors
26. Career IT Auditors
Sources for Career IT Auditors
People with Internal IT Audit Experience at Other
Companies
People with External IT Audit Experience
College Hires
IT Professionals
Sources for IT Professionals as Auditors
Technical Professionals from Within Your
Company
Technical Professionals from Outside Your
Company
College Hires
Forming and Maintaining an Effective
IT Audit Team
27. Ability to dig into technical details without getting
lost in the details.
Analytical skills.
Communication skills (both written and oral).
Ability to learn the key concepts of new
technologies quickly and identify key risk points
within those technologies.
Willingness not to be touching a specific
technology daily.
Build trust-based relationships with their
customers.
Key Traits of a Successful IT Auditor
28. Exposure to a wide variety of technologies
Opportunity to work with many levels of
management.
Broad view of the company and other IT groups
Opportunity to lead projects.
Selling Points for Recruiting IT
Professionals into IT Audit
29. Co-sourcing
Sources of Learning
Formal Training
Research Time
Specialization
Knowledge Sharing After Training
Certifications
Job Swaps with the IT Organization
Combining Options and Maintaining Skills
Maintaining Expertise
30. May be viewed as an intrusion and an
annoyance.
Must be a healthy working relationship between
the internal and external auditors.
Keep the other informed of their activities.
Encourage the external auditors to review the
internal auditors’ work prior to speaking with
your customers (customer : organization
demanding audit from an external auditor).
Relationship with External Auditors
Editor's Notes
#9:Internal controls: Examples include use of passwords, approval, policies and procedures.
#11:There’s a big difference image-wise between saying that a system doesn’t matter to you and saying that you want to
provide sign-off as usual but that you don’t have many concerns: one is a negative message,
and the other is positive.
#13:1. The audit department should agree on the timing and scope of the informal
review with the people who are to be audited.
2. The auditor who will be performing the review should create a basic checklist
of areas that will be under review. (The checklists throughout this book
provide a good starting point.)
3. The auditor executes those steps, keeping notes as needed but not creating
work papers for review. The notes do not need to be kept after the audit is
completed. Remember that speed is of the essence, and this is a consulting
engagement, not a formal audit review. If you can’t get comfortable with this,
you’ll get bogged down with documentation and process, losing the flexibility
to perform this sort of review effectively.
4. At the end of the project, the auditor compiles all concerns from the review.
5. The auditor has a debriefing meeting with the people who were audited to
discuss the issues and consult about how serious the issues are and potential
means for addressing them.
6. The auditor documents the final list of concerns, along with relevant thoughts
on resolving them, in a memo. This memo does not need to include due
dates and can include the caveats mentioned earlier (for example, this is not
a formal audit, we will not be tracking issues, and so on). The memo also
should indicate the auditor’s willingness to continue consulting with the
team as it addresses these items.
7. The auditor issues the memo and archives it electronically for future reference.
#15:Guidelines on Internal Controls
www.sbp.org.pk/bsd/2004/Anex-C7.pdf
#28:Willingness not to be touching a specific technology daily. although performing audit analyses requires a lot
of hands-on work, they won’t be acting as the administrator of a production Unix box, managing routers, and so on.
Relationship building skills. Auditors must be able to build solid trust-based
relationships with their customers.
#30:Co-sourcing is a business strategy that involves combining internal and external resources to achieve a common goal.