GRC Oversight

Live demoFictional sample data. Nothing is saved.

Sign up
Northwind Robotics

02Overview

Assistant

Ask ChatGRC about Northwind Robotics's compliance program: framework readiness, which controls are failing, policies, evidence, and open risks. Every answer is grounded only in your organization's data and cites what it used.

  • Which controls are currently failing, and what's the fastest one to fix?

  • Northwind Robotics has 2 controls in a failing state out of 41 mapped controls. 1. CC7.2: Security events monitored (Security, 68% coverage). 3 endpoints missing centralized log forwarding. 2. A.8.16: Monitoring activities (Platform, 73% coverage). Evidence is 41 days stale; last collection failed silently. A.8.16 is the faster fix: it's a stale-evidence issue, not a real control gap. Re-running the AWS CloudTrail collector should refresh it within a day. CC7.2 needs the 3 endpoints onboarded to the log pipeline first.

    Sources

    • [1] Control CC7.2: Security events monitored
    • [2] Control A.8.16: Monitoring activities
    • [3] Evidence: AWS CloudTrail export, 41 days ago

  • Do we have a policy that covers vendor offboarding?

  • Yes, the Vendor Management Policy (v3, approved by Marcus Bell) section 4.2 covers offboarding: access revocation within 5 business days of contract end, and a final data-return or destruction attestation from the vendor. It's mapped to control CC9.2 and was last reviewed 74 days ago, within your 12-month cadence.

    Sources

    • [1] Policy: Vendor Management Policy v3, §4.2
    • [2] Control CC9.2: Vendor offboarding

Try another prompt