DOCSLIB.ORG

Separation of Duties in Information Technology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Separation of Duties in Information Technology Separation of Duties in Information Technology John Gregg, Michael Nam, Stephen Northcutt and Mason Pokladnik Separation of duties is a classic security method to manage conflict of interest, the appearance of conflict of interest, and fraud. It restricts the amount of power held by any one individual. It puts a barrier in place to prevent fraud that may be perpetrated by one individual. Fraud will still occur if there is collusion. To be certain that you have identified all separation of duties issues, you will first need to create an information flow diagram for every function within each area of the organization. However common sense can help identify a large number of situations where separation of duties is appropriate. For instance, positions that handle money, valuable items, and new and attractive items (think iPad after it first came out), require a number of controls. Although there are a number of similar controls among organizations, specific controls are relatively different between industries. There is no complete matrix that may be applied to all organizations. separation of duties within each company is unique. Since separation of duties equates to additional cost because it often increases head count, a risk assessment should first be performed to determine whether it is necessary, or whether compensating controls are adequate. As you are aware, management may decide to accept, reject, or divert the risk instead of controlling the risk through separation of duties. It is a balance between the cost and the amount of risk being considered and addressed. Once this is decided, management may determine where separation of duties will be applied. Note: John Gregg from UC Davis, developed a self assessment for determining risk related to separation of duties, it is available here .[1] To expand on positions concerning money: in general, one person should indicate the action related to money inflow or outflow, another verifies that action has happened or causes the action to happen. It is very common for accounting divisions to have this separation. Examples: A salesperson may take orders, but someone else marks the order paid. The fulfillment department ships the product. The accounts receivable clerk matches the customer order to the shipment sent before charging the customer. A purchasing agent may have the authority to bind the company to purchase orders up to a specific amount. Their supervisor should be required to approve purchase order over that amount. After the product is received, the accounts payable clerk matches the purchase order, bill of lading, and invoice before payment is made. Internal and External Auditors perform similar functions. To have External Audit review the internal controls and financial statements of a company is not a separation of duties issues. External Audit is an independent party that reviews the work of Internal Audit, internal controls, and financial records of the company. External Audit's assessment is for the general shareholders, while the Internal Audit's assessment is primarily for management and the board of directors. Building contractors and their subs do the work, county impartial inspectors evaluate the work to ensure that it meets the current building code. In fact, in industry there are numerous examples of "doers and inspectors". Separation of duties in Information Technology The technology group should understand the basic separation of duties issues within the technology area as well as the principle of least privilege. However, technology does not normally have the expertise to determine the separation of duties issues within the business. Although conflicting access rights may be a cause for concern, it is not technology's responsibility to identify these separation of duties issues. However, following the reasonable person rule, technology does have the responsibility to bring a separation of duties issue to management attention when they observe them. The audit function usually has more training and expertise to map business logic to information flow and suggest where separation of duties makes sense. Ultimately, it is business management's responsibility to adequately address separation of duties issues. For daily operational purposes, Compliance may be sought to review user access rights to address separation of duties concerns. Internal Audit would review user access during audits for separation of duties issues. Note that Internal Audit would not do it on a daily operational basis as it would become a separation of duties issues for Internal Audit. Where Internal Audit performs this function, Internal Audit will not have the appearance of being objective during their audit. Intellectual property is the lifeblood of an organization and process should be designed to protect it. Some specific tips: Software developers should never have access to production systems. Production systems should not have compilers installed. A configuration management board or equivalent should be involved in the decision to place code that has been developed into a production environment. No code should ever be installed in a production environment that has not been approved. As a general principle development and production should always be separate with no crossover (at a minimum, the root/administrator password on development systems should not work on production systems. Better practice is not to allow developer accounts on production systems and to use network access control so that developer VLANS cannot access production systems other than office automation production systems so they can read their email.) Developers may be granted access to production for emergency changes using pre-established accounts for this purpose at the time of need. Controls need to be implemented to administer distribution. Emergency change procedures should only be initiated for operational problems occurring at night where a process must be completed and developer intervention is required. Additional controls will need to be implemented to ensure that changes are tested and approved properly. This problem is not unique to software development. Change control can be applied to many operational aspects of IT as well, such as having a manger approve firewall rule changes before they are applied. Source code, or other intellectual property repositories should always have a monitoring counter to detect excessive use. For instance, SANS might have a courseware repository. Since courses are commonly six days, but there might also be lab manuals, the counter might be set to ten. When an instructor is preparing to teach a class, they download the latest version of the courseware for each day. However, if they download more than ten files from the repository over a certain span of time, an alert might be sent to management or it could even trigger an account logout. Backups are important and we want to encourage backups, but not everyone that has administrator or super user privilege should be allowed to create backups since this gives them a copy of all of the intellectual property. Approved backup operators should be identified in writing with the appropriate procedures. In general, it is far safer to use disk replication to an alternate site. Backups made to small tapes that easily fit in a pocket or briefcase are the highest risk. Backup tapes may need to be produced for regulatory compliance and should be protected in a manner consistent with the sensitivity of the information. Outsourced maintenance personnel should be restricted to the systems they are working on. This can be done by creating a unique VLAN, or DMZ, or using tools like Exceedium or sometimes referred to as Xceedium. All contractors should have contracts that meet the company's privacy requirements, including non-disclosure agreements. A vendor management policy and privacy policy should be implemented and enforced. Privacy Policy needs to address the data classification of intellectual property. Network and Security administrators have the ability to see anything that is sent across the network. Only authorized sniffers may be used. Only authorized signature sets may be used. When possible, portable sniffers should not be used; use investigation enterprise level devices with a console. Only with written permission should the sniffer be a piece of software on the network administrator’s laptop; it is highly recommended to have a corporate device stored appropriately and checked out for use as needed. Database administrators are the hardest position to control. If you want the database to work, all tables probably have to join. DBAs should only have DBA authority, not root or administrator. It may be possible to encrypt the content of some sensitive fields in the database. Consider tools that manage and audit database access, such as Imperva. All activity for accounts with elevated privileges should be logged and reviewed daily by an independent party. It should be noted that Oracle has made significant progress in the past few years to allow separation of duties. To enforce accountability, generic administrative accounts should be disabled - and an alert issued if they are used - since generic accounts can be used to bypass role-based access controls. In addition, the principal of least privilege suggests that each Administrator and DBA should have two accounts, one with elevated rights and one with normal user rights. The normal account should be used to perform mundane functions such as checking email, while the account with elevated rights should only be used to perform tasks requiring administrator\\\\super user level access. If a process is particularly sensitive, two factor authentication may be used to further ensure that the person performing the task is the person authorized to do so. Logging for systems, network equipment, databases, etc., should be directed to a write-only logging system. The logging system should be administered by a group separate from the people responsible for network and systems administration, and access to the logging system should be role-based so that administrators may only see the logs for their own systems.
Load more

Recommended publications
  • AHA 2018 Accounting Policy
    Albuquerque Housing Authority Accounting Policy 2018 Revised Edition 1840 University Boulevard SE Albuquerque, NM 87106 Phone: (505) 764-3920 Fax: (505) 764-3981 www.abqha.org Albuquerque Housing Authority Accounting Policy Contents Introduction ......................................................................................................................................................................... 3 Housing Authority & Compliance ................................................................................................................................... 3 Department of Housing & Urban Development (HUD) ....................................................................................... 3 HUD Financial Assessment.......................................................................................................................................... 4 Financial Compliance .................................................................................................................................................... 4 Compliance with External Policies .............................................................................................................................. 5 Board Authority .................................................................................................................................................................. 5 Board of Housing Commissioners .............................................................................................................................
    [Show full text]
  • Internal Control Guidance (Pdf)
    Kansas State University Internal Control Guidance Purpose The internal control guidelines seek to: • Provide practical tools for those charged with responsibility to process transactions. • Maintain custody of resources. • Communicate established policies and procedures. • Convey the definition of internal control. Key Guidelines Benefits of Effective Internal Control Purpose 1 One of the most misunderstood roles of internal control is the belief that it exists solely to prevent or reduce fraud. In reality, Benefits of Effective Internal Control 1 the purpose of internal control is much more broad. Benefits include: Consequences of a Lack of Internal Control 1-2 • Reliable reporting to support management decisions. • Consistent, efficient methods to process transactions. Concepts of Internal Control 2 • Compliance with university, state and federal regulations. Risk Assessment 2 Effective controls also can reduce instances of noncompliance and negative publicity with grant rules and legislative Information Technology (IT) Controls 3 dictates. These controls ensure continued good relations with students, legislators, the Kansas Board of Regents, grantors, Information and Communication 3 donors and Kansas taxpayers. Effective internal control does more than simply satisfy auditors or central administration. It allows for effective, efficient operations by providing reliable information and compliance with regulations that protect Reporting Fraud and Misconduct 4 future funding. Monitoring 4-5 Control Activities 4 Consequences of a Lack of Internal Control To illustrate the need for controls in a variety of risk areas, we have included the following excerpts from the Auburn Physical Controls 5 University Office of Audit, Compliance and Privacy newsletter. The names of individuals, states and institutions have been Transaction Authorization 5 omitted, and none are from the state of Kansas.
    [Show full text]
  • Internal Controls and the Internal Auditor Presented By: Richard Kudlik, CPA Interrelated Components
    Internal Controls and the Internal Auditor Presented By: Richard Kudlik, CPA Interrelated Components Control Environment Risk Assessment Control Activities Information and Communication Monitoring What is an Internal Control? Internal control is broadly defined as a process, …….. effected by an entity's board of directors, management and other personnel,……… designed to provide reasonable assurance…….. regarding the achievement of objectives in the following categories: Protect District assets. Effectiveness and efficiency of operations. Reliability of financial reporting. Compliance with applicable laws and regulations. Limitations of Internal Control 1. Management Override Management may override the structure to commit fraud or misstate the financial statements. 2. Human Errors Human errors may arise from misunderstanding of instructions, mistakes of judgment, and personal carelessness, distractions, or fatigue. 3. Collusion Collusion may circumvent the separation of duties. 4. Changing Conditions Conditions may change, weakening a system that was adequate at a point in time. 5. Combination of duties One employee is performing conflicting job duties (lack of segregation of duties). Control Characteristics When identifying controls within processes – consider the characteristics of those controls Preventative Controls that minimize the possibility of an error or deliberate misstatement Examples: building access cards, segregation of duties, no price change without supervisor’s access code Detective Controls that
    [Show full text]
  • Internal Control Liability Concerns Post Sarbanes-Oxley: Perspectives on Legal Liability and Reasonableness
    Journal of Forensic & Investigative Accounting Vol. 2, Issue 2 Internal Control Liability Concerns Post Sarbanes-Oxley: Perspectives on Legal Liability and Reasonableness Richard Mark Roberta Ann Barra Martin E. Taylor* 1. The Role of the Accounting Profession in Internal Control With passage of the Securities Act of 1933 (the 33 Act) and the Securities Exchange Act of 1934 (the 34 Act), Congress directed the SEC “to protect the public from false and misleading information by requiring publicly-owned corporations to disclose financial and other information in a manner which accurately depicts the results of corporate activities. Congress gave the SEC broad authority to establish accounting and reporting standards as part of its mandate to administer and enforce the provisions of the Federal securities laws.”1 The Securities Acts also created a need for accountants to act as independent auditors by requiring that certain information reported to the public by corporations be independently certified.2 Under the 33 and 34 Acts, the SEC had the authority over the establishment of accounting and auditing standards. The SEC decided not to exercise that authority, but instead to rely upon accounting and auditing * Richard Mark and Martin E. Taylor are, respectively, Associate Professor and Professor, both at the University of Texas at Arlington. Roberta Ann Barra is an Assistant Professor at the University of Hawai’i at Hilo. 229 standards established by the private sector as long as these standards had “substantial authoritative support”.3 Over the years, three bodies provided authoritative support for accounting standards: The Committee on Accounting Procedure (CAP), the Accounting Principles Board (APB) and, currently, the Financial Accounting Standards Board (FASB).
    [Show full text]
  • Chapter 7 Questions Multiple Choice 1
    Chapter 7 Question Review 1 Chapter 7 Questions Multiple Choice 1. The entry to replenish a petty cash fund includes a credit to a. Petty Cash. b. Cash. c. Freight-In. d. Postage Expense. 2. A $300 petty cash fund has cash of $39 and receipts of $255. The journal entry to replenish the account would include a. debit to Cash for $255. b. credit to Petty Cash for $255. c. debit to Petty Cash for $261. d. credit to Cash for $261. 3. A $150 petty cash fund has cash of $21 and receipts of $126. The journal entry to replenish the account would be a. Cash 126 Petty Cash 126 b. Miscellaneous Expenses 126 Cash Over and Short 3 Cash 129 c. Miscellaneous Expenses 126 Cash Over and Short 3 Petty Cash 129 d. Miscellaneous Expenses 129 Cash Over and Short 3 Cash 126 4. The reconciliation of the cash register tape with the cash in the register is an example of a. other controls. b. independent internal verification. c. establishment of responsibility. d. segregation of duties. 5. Which of the following is not an internal control procedure for cash? a. Payments should be made with cash. b. There should be limited access to cash. c. The amount of cash on hand should be kept to a minimum. d. Cash should be deposited daily. Chapter 7 Question Review 2 6. The following information was taken from Niland Company cash budget for the month of April Beginning cash balance $120,000 Cash receipts 108,000 Cash disbursements 136,000 If the company has a policy of maintaining an end of the month cash balance of $100,000, the amount the company would have to borrow is a.
    [Show full text]
  • Sub-Functions and Components ______
    7460.7 REV-2 CHAPTER 4: SUB-FUNCTIONS AND COMPONENTS ___________________________________________________________________________ SECTION 4: SUB-FUNCTIONS AND COMPONENTS 4-1 MAJOR AREAS OF OPERATION. For monitoring purposes, finance and budget activities have been separated into major areas of operation that are called "Sub-functions". These Sub-functions are further divided into "Components" that represent activities within the Sub-function. Each of the Sub-functions and Components are linked and as a result PHA performance in one area will affect the success or failure in others. 4-2 PHA SUB-FUNCTIONS. The success of a PHA depends on how it deals with Sub-functions in its daily operations. The major Sub-functions are as follows: 1.Establishing policies, procedures and/or systems 2.Maintaining budget and financial controls 3.Maintaining accounting books and records in accordance with HUD policy 4.Implementing internal controls 5.Financial reporting 4-3 PHA COMPONENTS. For each of the Sub-functions there are Components that the PHA is responsible for carrying out in an effective manner. The following paragraphs offer a brief description of each of the Components. 1.Budget and Financial Controls ======================================== 24 CFR 85.20 ======================================== a.All PHAs are required to effectively manage Federal funds. Budget and financial management controls must be established to ___________________________________________________________________________ __/__ 4-1 ___________________________________________________________________________ adequately monitor income and expenses. b.Budgeting is a major function of a PHA. A budget is a realistic projection of operating receipts and expenditures for a given period of time to be used as a plan of operation. It is also used to measure an agency's performance.
    [Show full text]
  • Appendix B: a School's Financial Management Systems
    A School’s Financial APPENDIX Management Systems a B The accounting procedures and financial management systems used by a school to record and report on the transactions in the Federal Student Aid programs play a major role in the school’s management of those programs. In this appendix, we will discuss the minimum criteria for those procedures and systems, identify areas where problems might arise, and point out poten- tial system weaknesses. FINANCIAL MANAGEMENT SYSTEMS Financial management systems 34 CFR 668, Subpart K A school’s financial management system (including the school’s accounting system) must provide effective control over and accountability for all funds received from the U.S. Department of Education’s (ED’s) Grant Management System (G5). An FSA fiscal management system includes procedures for: ◆ requesting funds from ED; ◆ disbursing funds to eligible students and parents; ◆ accounting for funds and financial activities;1 ◆ keeping accurate and auditable records including providing the clear audit trail required by cash management regulations;1 ◆ meeting the documentation requirements of the individual program regulations; ◆ managing cash; ◆ ensuring proper filing of timely applications; and ◆ enabling timely internal and external financial reporting. At a minimum, a school’s financial management system, including its accounting system, must provide: ◆ accurate, current, and complete disclosure of the financial condition of each federal aid program or project sponsored by ED; ◆ records that adequately identify the source
    [Show full text]
  • Section 5- Internal Control Activities & Best Practices
    Rhode Island Office of Internal Audit Internal Control Guide & Resources Section 5- Internal Control Activities & Best Practices Managers must establish internal control activities that support the five internal control components discussed in Section 2 of the Internal Control Guide. There are two main types of control activities. Controls can be either preventive, for example, requiring supervisory sign-off before an item is purchased, or detective, for example reconciling bank statements to ensure that all payments are appropriate. Examples of key internal control activities that agencies should establish and incorporate in an internal control structure are described in the following sections. Authority The various stages of a transaction or activity should be carried out and approved by employees acting within their range of knowledge and proper span of control. These stages include the processes of recording, approving, and reconciling. Best Practices: • Policies and procedures should clearly identify which individuals have authority to initiate, submit, reconcile, view or approve different types of transactions. • Employees should be properly trained and informed of departmental procedures related to internal controls. Individuals approving transactions should have firsthand knowledge of the transactions, or they should review supporting documentation to verify the validity and appropriateness of transactions. • The workflow process should stress timely authorizations as well as timely processing of transactions following approval. Workflow is an important aspect of good internal controls. Time lags between approval and processing provide opportunities for altered documents and potential fraud. 1 Rhode Island Office of Internal Audit Document Internal Controls and Maintaining Other Types of Documentation Documenting policies and procedures is especially important because change happens constantly.
    [Show full text]
  • CPO Internal Controls Webinar April 11, 2019 11:00 AM CT
    CPO Internal Controls Webinar April 11, 2019 11:00 AM CT Christie Hillsman: Good morning, everyone. Welcome to NFA's webinar, CPO Internal Controls. My name is Christie Hillsman, and I'm a Communications Manager at NFA. And with me today are Patty Cushing, Director of Compliance, and Ryan Ahlfeld, Manager II, Examinations, Compliance. As you know, NFA recently adopted a new Interpretive Notice titled CPO Internal Controls. The Interpretive Notice requires all CPO Members to implement an internal controls framework designed to protect customer funds, provide reasonable assurance that the books and records of a CPO's commodity pools are accurate and reliable, and that the CPO is in compliance with all CFTC and NFA requirements. The Interpretive Notice became effective on April 1, 2019. During this webinar we will discuss the requirements established in the Interpretive Notice. Following our prepared remarks, as well as throughout the webinar as appropriate, we've allocated ample time to answer any Member questions that might be submitted. To ask a question, locate the box labeled "Ask a Question" on the left side of your webinar screen. Please type the question you would like to ask into the box and click the "Send" button. We are able to see your questions as they are submitted. Please feel free to submit your questions now or at any time during today's webinar. For questions that are firm specific, note that we will reach out to you individually following the webinar. Additionally, a recording of this webinar along with a written transcript will be on NFA's website in the coming weeks, so no need to take detailed notes throughout this presentation.
    [Show full text]
  • Separation of Duties for System Security Administration and Auditing
    Chief Information Officer Office of Information Services Centers for Medicare & Medicaid Services CMS Operational Policy for Separation of Duties for System Security Administration and Auditing March 2006 Document Number: CMS-CIO-POL-INF07-01 TABLE OF CONTENTS 1. PURPOSE................................................................................................................................1 2. BACKGROUND.....................................................................................................................1 3. SCOPE.....................................................................................................................................1 4. OPERATIONAL POLICY....................................................................................................2 5. ROLES AND RESPONSIBILITIES.....................................................................................2 5.A. IT INFRASTRUCTURE SYSTEM ADMINISTRATORS ........................................................................ 2 5.B. IT INFRASTRUCTURE SECURITY ADMINISTRATORS ..................................................................... 3 5.C. CMS SECURITY AUDITORS........................................................................................................... 3 6. APPLICABLE LAWS/GUIDANCE.....................................................................................3 7. EFFECTIVE DATES .............................................................................................................4 8. INFORMATION AND ASSISTANCE.................................................................................4
    [Show full text]
  • Accounts Payable Process: Number: BP- 03
    State of Vermont Department of Finance and Management Financial Issue Date: July 2006 Accounts Payable Process: Number: BP- 03 Revision Topic: Internal Control - Best Practices N/A Date: Applicable All State Agencies, Departments, Page: 1 of 3 To: and Offices Objective Departments shall devise techniques and procedures for the proper approval and payment of expenditures of public monies for goods and services incurred to support its programs. Proper internal controls effectively and efficiently minimize the risks associated with accounts payable and purchasing activities, reduce the risks of fraud and costly errors, and protect the assets of the state. Risks o Unauthorized or fraudulent purchases/payments. (high degree of inherent risk) o Duplicate payments to vendors. o Payments to vendors prior to vendor terms which negatively impact the state’s cash flows. o Late payments to vendors resulting in late fees and loss of goodwill. o Inefficient processing of payments. Definition The term “accounts payable” refers to processing payments for invoices and contracts for goods and services incurred by the State of Vermont. (This document does not address “Petty Cash” disbursements which are discussed separately under Best Practices # 2 – Petty Cash.) Best Practices Include Written procedures should be established regarding the initiation, review and approval of all accounts payable expenditures. [Documentation] Invoice handling procedures should include written documentation of the processes for routing and forwarding of invoices for payment and the methods used to manage exceptions. [Documentation] Financial Issue Date: July 2006 Accounts Payable Process: Number: BP- 03 Revision Topic: Internal Control - Best Practices N/A Date: Applicable All State Agencies, Departments, Page: 2 of 3 To: And Offices Payables, disbursements and expenditures are properly accumulated, classified and summarized in the accounting records.
    [Show full text]
  • AUDIT INFORMATION PROJECT Presented by FINANCIAL AFFAIRS
    FINANCIAL AFFAIRS AUDIT INFORMATION PROJECT ___________________________________________________________________________ AUDIT INFORMATION PROJECT Presented by FINANCIAL AFFAIRS April 2008 7/17/2008 FINANCIAL AFFAIRS AUDIT INFORMATION PROJECT ___________________________________________________________________________ AUDIT INFORMATION PROJECT Table of Contents Introduction Audit Survival Guide Internal Controls Segregation of Duties Job Aids for the University Community Departmental Cash Receipts & Deposits Disbursements / Payroll / Misc Human Resources Petty Cash Purchasing Operations Purchasing pCard Travel Job Aids for Units Handling Cash, Credit Cards and PCI Compliance Additional Resources 7/17/2008 FINANCIAL AFFAIRS AUDIT INFORMATION PROJECT ___________________________________________________________________________ INTRODUCTION The Financial Affairs Audit Information Project is designed to assist departments and personnel at Florida Atlantic University with daily operations and how the operations may relate to audits and audit findings. The first presentation is the Audit Survival Guide which explains audits and how to prepare for one. The next two topics are ones that most often result in audit findings – Internal Controls and Segregation of Duties. The last section is a tool that can be used to help determine if current operations may result in an audit finding. If you have any questions, contact Purchasing, the Controller’s Office, the Office of the Inspector General, or Dianne Parkerson, [email protected]. 7/17/2008 FINANCIAL
    [Show full text]