Request failed with status code 502
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from `courses` where `id` = 12 limit 1)
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from `courses` where `id` = 12 limit 1)
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from `courses` where `id` = 12 limit 1)
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from `courses` where `id` = 43 limit 1)
SQLSTATE[HY000] [2002] Connection refused (SQL: select * from `courses` where `id` = 43 limit 1)

Compliance Management

Learn how to do ISO 27001, PCI-DSS, NIST, SOC2 or any other compliance requirement with eramba

  • Episodes18
  • Duration5h 31m 37s
  • LanguagesEN
Episode 11

Exception Management

Exception Management

 

  • The video discusses the concept of "exceptions" in the context of Governance, Risk, and Compliance (GRC) functionality in the Eramba software. There are three types of exceptions:

    • Risk exceptions: Used to document scenarios where no solution exists for a particular risk.

    • Compliance exceptions: Used to document compliance requirements that do not apply to the organization.

    • Policy exceptions: Used to document temporary exceptions to organizational policies.

  • The video walks through how to create, customize, and manage exceptions in Eramba, including setting expiration dates, linking to compliance requirements, and documenting decisions in the comments and attachments.

  • The video also covers setting up notifications and reports to monitor and manage exceptions, such as sending emails to exception owners before deadlines expire.