Audit Portal Training

Navigate GRC portals and submit audit evidence.

What You'll Learn

Training Steps

  1. Welcome to Apex Financial

    Welcome to Apex Financial Services! You are Alice, a client services representative who handles customer accounts and financial transactions. Today, you'll learn how to use the company's Security Audit Portal - a centralized system for reporting security concerns, tracking incidents, and ensuring regulatory compliance.

  2. Why Audit Portals Matter

    In financial services, security incidents must be documented properly for regulatory compliance (SOX, PCI-DSS, GLBA). The Security Audit Portal ensures: All security concerns are logged and tracked Incidents are routed to the right team automatically You can monitor the status of your reports The company maintains an audit trail for regulators

  3. A Suspicious Email Arrives

    Alice receives an email that doesn't feel right. It claims to be from a vendor requesting updated payment information, but something seems off about the formatting and urgency. Rather than ignore it or try to investigate alone, Alice decides to report it through the proper channel.

  4. Identifying Red Flags

    Before reporting, Alice takes a moment to identify what specifically makes this email suspicious. This information will help the security team investigate.

  5. Accessing the Audit Portal

    Now Alice will access the Security Audit Portal to submit a report. The portal is available at audit.apexfinancial.com and requires authentication for security purposes.

  6. Understanding the Dashboard

    The Audit Portal dashboard shows several key sections: New Report - Submit a new security concern My Reports - Track reports you've submitted Knowledge Base - Learn about security threats Emergency Contacts - Direct lines to security team Alice clicks 'New Report' to begin documenting the suspicious email.

  7. Selecting Report Type

    The portal offers several report categories. Choosing the right type ensures your report is routed to the appropriate team. Phishing/Social Engineering - Suspicious emails, calls, or messages Data Breach/Exposure - Potential unauthorized data access Policy Violation - Internal policy concerns Physical Security - Unauthorized access, tailgating Other - Anything that doesn't fit above

  8. Completing the Report Form

    Alice fills out the report with specific, factual details. Good reports include: What happened (received suspicious email) When it occurred (today's date/time) Who was involved (sender details) Why it's suspicious (red flags identified) What action was taken (no links clicked, reporting now)

  9. Report Submitted Successfully

    The portal confirms Alice's report has been submitted. She receives a ticket number (SEC-2024-0847) for tracking. The report is now in the security team's queue for review. Most reports are triaged within 4 hours during business days.

  10. Tracking Your Reports

    The 'My Reports' section shows all reports Alice has submitted. Each entry displays: Ticket ID - Unique reference number Type - Report category Status - New, In Progress, Resolved, Closed Priority - Assigned by security team Last Updated - Most recent activity