Comprehensive Study Notes: IT General Controls, Recovery Planning, and Fraud Schemes

Exam Regulations, Logistics, and Preparation Strategies

  • Desk Environment and Permissible Items:

    • During the exam, desks must be completely clear of all materials except for three mandatory items: a phone, a writing utensil, and a student ID card.
    • Students are permitted to have a water bottle at their desk.
    • Scratch paper is provided directly by the instructor.
    • The exam is administered on school computers using the Desire2Learn (D2L) platform.
    • No notes, course materials, or outside aids are permitted.
  • Time Allocation and Free Response Strategy:

    • Reserve at least 20 minutes20\text{ minutes} specifically for the written free response section.
    • Recommended exam strategy:
      1. Immediately review the free response questions upon starting the exam.
      2. Jot key prompt details and initial thoughts down on the provided scratch paper.
      3. Proceed through the multiple-choice section of the exam, actively scanning for specific terminology, technical vocabulary, and phrasing.
      4. Utilize the language and concepts found within the test questions to assist in constructing comprehensive written responses.
  • Exam Scope and Point Distribution:

    • The exam covers six chapters: Chapters 11, 22, 33, 88, 1414, and 1515.
    • The free response section is valued at approximately 33 points33\text{ points}.
    • The free response portion consists of multiple interconnected questions centered around a scenario structure designed to test integrated understanding.
  • Performance Trends and Post-Exam Reflection:

    • Exam 1 typically yields lower scores due to the sheer volume of new material presented at once.
    • A mandatory/bonus reflection assignment must be submitted within 24 hours24\text{ hours} following the exam.
    • The reflection requires students to evaluate:
      • Study strategies that were effective.
      • Study strategies that failed.
      • Planned changes for future exam preparations.
      • Specific exam areas that proved more difficult than anticipated.
  • Core Behaviors of Top-Performing Students:

    • Early Preparation: Successful students begin studying immediately and do not delay preparation until the day before or the morning of the exam.
    • Project Engagement: Consistent effort is applied to course projects throughout the semester, as projects are directly aligned with exam concepts.
    • AI Tool Utilization: Top performers actively design custom study prompts using AI tools to simulate exam conditions and test knowledge retention.
    • Peer Collaboration: Students engage in active retrieval practice by prompting peers to explain complex concepts from scratch without referring to notes.

AI Study Tools, Study Plans, and Course Assignments

  • Optimizing AI Study Tools for Active Recall:

    • Traditional study guides are often ineffective because answers are displayed directly in front of the student, preventing true self-testing.
    • AI tools can act as virtual study partners, prompting students with questions without revealing answers upfront.
    • Users can customize question difficulty, request free-response practice prompts, and track historical performance by topic.
    • Limit AI question generation to approximately 1515 questions per topic. Generating up to 5050 questions leads the AI to focus on irrelevant minutiae rather than core concepts.
    • Input the course topic breakdown into the AI tool to generate a balanced study schedule that allocates time proportional to topic weights.
  • Exam Breakdown and IT General Controls (ITGC):

    • IT Operations and Security Controls combined with COBIT account for 15%15\% of the total exam material.
    • IT General Controls (ITGC) are feathered throughout multiple chapters across the exam rather than confined to a single section.
    • Critical thinking must complement study guides and AI tools; students should trust instincts developed from class attendance when prioritizing topics.
  • Assignment Rules and Submissions:

    • Chapters 14 & 15 Homework: Counts as bonus points.
    • Chapter 8 Bonus Assignment: Involves a peer review of another group's flowchart.
      • Groups exchange flowcharts and evaluate them for errors, completeness, and logic.
      • Submissions must include a copy of the peer group's flowchart along with detailed feedback.
      • Only one group member needs to submit the assignment for the entire group to receive credit.
      • The assignment provides practical experience identifying structural and logical errors in flowcharts created by novice authors.

Chapter 14: IT General Controls — Business Continuity and Disaster Recovery

  • Role of ITGC in Operations:

    • Organizations often implement access controls and security controls but fail to invest adequate time, effort, and budget into business continuity and system failure recovery.
    • Because modern business processes are thoroughly integrated with IT infrastructure, maintaining core operations requires maintaining IT infrastructure availability.
  • Business Continuity Planning (BCP):

    • Definition: A comprehensive set of procedures designed to ensure that essential business operations continue running during a major disruption or disaster.
    • Scope: Does not guarantee the continuation of the entire business, but protects core, mission-critical business processes.
    • Maintenance: BCPs must undergo continuous maintenance and updates as business operations, systems, and processes evolve.
    • Cost & Complexity: BCP is significantly more expensive and requires far more planning than disaster recovery because operations must remain functional throughout the disruption.
  • Disaster Recovery Planning (DRP):

    • Definition: A subset of Business Continuity Planning focused strictly on restoring systems and resuming operations after a disaster or disruption has occurred.
    • Core Assumption: DRP assumes business operations will temporarily halt entirely, and efforts are directed at bringing systems back online.
    • Implementation Progression: Organizations starting from scratch should build a robust Disaster Recovery Plan first before expanding into a full Business Continuity Plan.
  • Downtime Tolerance Across Industry Types:

    • High Downtime Tolerance: Businesses that can sustain system outages for several days to a week without collapsing require basic DRP rather than continuous BCP.
    • Zero/Low Downtime Tolerance:
      • Transaction-Heavy Entities: Companies processing massive daily transaction volumes (e.g., Amazon, credit card processors, financial institutions) suffer severe financial loss from even brief downtime and require continuous BCP with mirrored/hot backup sites.
      • Hospitals: Require robust continuity plans for critical patient systems and power, as modern operations rely entirely on electronic medical records.
      • Airlines: Failures in continuity systems (e.g., legacy system crashes or widespread outages like CrowdStrike) lead to national operational paralysis. In past airline crises, flight-tracking systems were prioritized as critical assets, but employee staffing/scheduling recovery systems were not, preventing flight crew assignments and grounding operations nationwide.
    • Historical Impact (World Trade Center, September 11):
      • Prior to September 11, 2001, inadequate DR/BCP was the single most common IT audit management letter finding.
      • Following the events of September 11, 85%85\% of affected businesses in the World Trade Center that lacked adequate backup and recovery plans failed to reopen or resume operations.

Recovery Sites, Recovery Metrics, and Backup Strategies

  • Backup Recovery Site Classifications:

    • Hot Site (Mirrored Site):
      • Configuration: A fully operational physical facility equipped with functional hardware, pre-configured computers, power, water, network connections, and live data access.
      • Operation: Often maintained as redundant, active sites operating below 100%100\% capacity so that if one facility fails, traffic automatically reroutes to remaining sites without operational interruption.
      • Cost & Speed: Highest cost option due to total infrastructure duplication; provides the fastest recovery speed (near-zero downtime).
    • Warm Site:
      • Configuration: A physical location with active utilities (power, water) and physical hardware/computers present, but systems are not powered on or fully configured with live operational data.
      • Third-Party Vendors: Often operated by third-party service providers who pool site access across non-competing corporate clients for a recurring monthly fee.
      • Geographic Risk Management: Vendor clients must be geographically dispersed (e.g., avoiding clustering clients in nearby locations like Canton, Kennesaw, and Marietta) to ensure localized disasters do not trigger simultaneous demand by multiple clients exceeding site capacity.
      • Risk Strategy: Represents a Risk Transfer strategy (similar to insurance), shifting recovery infrastructure management to a third party.
    • Cold Site:
      • Configuration: A leased or owned space with baseline power and water, accompanied by hardware asset lists and pre-arranged purchase orders. No hardware or data is installed on-site beforehand.
      • Cost & Speed: Lowest cost option; results in the slowest recovery speed as equipment must be purchased, delivered, and configured post-disaster.
  • Key Recovery Metrics:

    • Recovery Time Objective (RTO):
      • The target duration of time within which business processes must be restored following a disruption.
      • Shorter RTO requirements demand more expensive recovery sites (Hot/Warm sites).
    • Recovery Point Objective (RPO):
      • The maximum acceptable age of files that must be recovered from backup storage for operations to resume successfully.
      • Represents the amount of data loss (measured in time) an organization can tolerate.
      • Shorter RPO requirements require more frequent data backup cycles.
  • Data Backup Types and Characteristics:

    • Physical Separation: Data backups must be stored on systems and physical locations entirely separate from primary production environments. (e.g., A California firm hit by ransomware lost both primary data and backups because backups were hosted on the same compromised network).
    • Full Backup:
      • Copies the entirety of the targeted dataset.
      • Requires the longest execution time and maximum storage space.
      • Highest cost; enables the fastest data restoration process.
    • Incremental Backup:
      • Copies only the data that has changed since the most recent backup (whether full or incremental).
      • Requires minimal storage space and executes very quickly.
      • Lowest cost; results in a slower and more complex restoration process, as it relies on the integrity of all prior incremental backup files in the chain.
  • Grandfather-Father-Son (GFS) Backup Rotation Scheme:

    • Grandfather: Full backup performed on a monthly basis.
    • Father: Intermediate backup performed on a weekly basis.
    • Son: Incremental backup performed on a daily basis.

Backup Power, System Shutdown, and Recovery Control Testing

  • Backup Power Infrastructure:

    • Power outages represent common disruptive events that require explicit disaster response planning.
    • Data centers require short-term backup power solutions, such as Uninterruptible Power Supplies (UPS) or automated generators.
    • The primary purpose of data center backup power is to sustain operations long enough (typically 15 to 20 minutes15\text{ to }20\text{ minutes}) to execute a clean, systematic shutdown of servers, preventing severe data corruption.
  • Testing Recovery Controls:

    • Recovery controls (such as BCPs, DRPs, backup power, and fire suppression systems) are only activated during disruptions and will fail if not routinely tested.
    • Fire Suppression & Elevators: Physical assets undergo mandatory periodic testing documented by physical inspection tags/certificates.
    • Data Backup Failure Example: An IT audit client performed daily and weekly tape backups for an entire year, storing them in a portable fireproof box. However, because they never tested a data restoration, they failed to discover that the storage location demagnetized the tapes. During a live power outage, all backup data was found unreadable.
    • Cloud Backup Misconceptions: Cloud storage does not eliminate the need for backup oversight. Organizations must review cloud providers' System and Organization Controls (SOC) reports and maintain secondary local copies to mitigate the risk of cloud-provider disasters.

Program Change Control and Change Management Lifecycle

  • Definition and Core Purpose:

    • Program change control (change management) ensures that all modifications to software and IT infrastructure are authorized, tested, and approved prior to live deployment, preventing system failure, security vulnerabilities, and fraud.
  • Three/Four-Stage Change Lifecycle:

    1. Development Environment: Programmers construct software modifications in a completely isolated environment that contains no live operational data or active users.
    2. Test Environment: Completed code is migrated to a test environment where independent testing personnel evaluate the changes to confirm proper functionality and obtain formal approval.
    3. Staging Environment: An optional intermediate holding area where fully tested and approved changes reside until a scheduled deployment window, avoiding constant system interruptions.
    4. Production (Live) Environment: The active operational environment utilized by end users. System access to upload code directly into production is strictly restricted to a very small number of authorized individuals.
  • Normal vs. Emergency Changes:

    • Normal Changes: Move sequentially through Development, Test, Staging, and Production environments.
    • Emergency Changes: High-priority updates applied directly to the Production environment to resolve critical operational failures.
    • Post-Emergency Requirement: Following an emergency patch, the implemented code must immediately be processed retroactively through the standard Development and Test pipeline to ensure proper documentation, approval, and security compliance.
  • Change Control Failure Case Studies:

    • University System Deployment: Operational staff modified a network master image template without adequate testing and deployed it across campus workstations. The untested code wiped 35%35\% of all university computers, displaying blue/black error screens. Recovery required individual machine restoration based on system backup schedules.
    • Litigation Data Security: During World Trade Center property valuation litigation, a consulting firm spent over $500,000\$500,000 compiling proprietary financial datasets. Two days after a judge ruled the firm was not required to share its compiled dataset with opposing counsel, burglars broke into the firm's offices and stole only the computer towers—leaving behind cords, mice, and cash. Because the firm maintained off-site cloud backups, no operational data was lost.

Chapter 15: Occupational Fraud and Asset Misappropriation

  • Three Primary Categories of Occupational Fraud:

    1. Corruption: Schemes such as bribery, conflicts of interest, illegal gratuities, and economic extortion (contains 44 specific sub-types).
    2. Asset Misappropriation: Theft or misuse of organizational assets (most common form of occupational fraud).
    3. Financial Statement Fraud: Intentional material misrepresentation of financial statements (least common, but most costly form of fraud).
  • Asset Misappropriation Subcategories:

    • Cash Receipts Schemes:
      • Skimming: Theft of incoming cash funds before they are recorded in the accounting system (off-book fraud).
      • Larceny: Theft of cash after it has already been recorded in the accounting records.
      • Trend: Unconcealed larceny has increased because fraudsters recognize that concealment activities are the primary source of audit detection. By omitting concealment, fraudsters hide in plain sight, convert stolen funds quickly, and abscond before the discrepancy is noticed.
    • Fraudulent Disbursements (Most Common Cash Asset Misappropriation):
      • Expense Reimbursement Schemes:
        • Double Dipping: Submitting the exact same business expense multiple times (e.g., using a physical receipt for one claim and an electronic invoice for another, or altering receipt dates).
        • Cash Claim Abuse: Claiming high-value business expenses (e.g., hotel bills) were paid in cash to avoid providing matching credit card statements. Organizations enforce strict payment policies to block this avenue.
      • Payroll Schemes:
        • Ghost Employees: Setting up fictitious individuals in the payroll system to receive direct deposit payments.
        • Falsified Hours/Falsified Work: Claiming compensation for unworked hours or manipulating physical time clocks (e.g., buddy punching or clocking in remotely via personal devices).
      • Billing Schemes:
        • Setting up fictitious vendors in the accounts payable ledger and submitting false invoices to generate check disbursements to fraudster-controlled accounts.

Financial Statement Fraud Mechanisms and Management Override

  • Core Concepts of Financial Statement Fraud:

    • Financial statement fraud involves intentionally misstating financial numbers to mislead external readers.
    • Overstating Financial Performance (To look better):
      • Income Statement: Overstate Revenues OR Understate Expenses (both increase Net Income).
      • Balance Sheet: Overstate Assets OR Understate Liabilities.
    • Understating Financial Performance (To look worse, e.g., tax avoidance or stock manipulation):
      • Income Statement: Understate Revenues OR Overstate Expenses (both decrease Net Income).
      • Balance Sheet: Understate Assets OR Overstate Liabilities.
  • Specific Revenue and Expense Manipulation Schemes:

    • Sham Sales / Fictitious Revenues: Recording completely fabricated sales transactions that never occurred.
    • Cutoff Manipulation:
      • Altering the accounting period boundaries to artificially shift transaction timing.
      • Example: Including December 31 or February 1 sales transactions in the January financial report to artificially boost January revenue.
      • Cascading Effect: Manipulating cutoff periods creates severe shortfalls in subsequent accounting periods, forcing the fraudster to engage in progressively larger frauds to cover the compounding deficit.
    • Unauthorized Shipments: Generating fake shipping documentation without customer orders to prematurely recognize revenue upon dispatch.
  • Management Override of Controls:

    • A recurring cause across both operational and financial statement frauds is the ability of management to override established internal controls.
    • Upper management possesses administrative authority to bypass control checkpoints that prevent lower-level employee fraud.
    • Neutralizing management override requires establishing a strong control environment, independent audit committees, and rigorous internal control structures.