Why did we build this product?

The rise of AI regulations globally (EU AI Act, U.S. Executive Order, state-level laws) is creating urgent demand for organizations to identify and manage their AI-related risks. Our customers need a way to evaluate their AI systems and ensure compliance across jurisdictions, frameworks, and internal policies, while also ensuring a defensible audit trail. AI Risk is our response to that need.

What problem is AI Risk solving?

AI Risk provides a structured and defensible assessment process to identify and document risks tied to the use of AI systems. It supports organizations in evaluating regulatory exposure, applying consistent risk frameworks, and establishing AI governance across legal, privacy, security, and compliance teams.

Who will use this product?

AI Risk is intended for cross-functional teams that include Compliance, Legal, AI Governance, and Risk Management. AI Steering committees and their component members. AI steering committees and executives responsible for AI governance risk and compliance will find this especially valuable.

What makes this different from other AI governance tools?

Unlike general-purpose risk registers or generic GRC tools, AI Risk: Codifies regulatory guidance (e.g., EU AI Act, NIST RMF) into configurable assessments. Supports multi-framework alignment and documentation. Provides built-in auditability and traceability.

What are the top use cases?

Regulatory Alignment: Mapping AI systems to the EU AI Act or NIST AI RMF. Pre-Deployment Review: Assessing risk before releasing a model or tool. Cross-Functional Collaboration: Legal, compliance, and AI teams jointly evaluating risk. Audit Trail: Documenting decisions and rationale for audits and regulators.

Will this tie into incident workflows?

Yes. Incidents involving AI system misuse or harm can trigger assessments. Likewise, risk findings can link back into Compliance or Privacy obligations when thresholds are met.

Can I see reporting by risk level or framework coverage?

Yes. Assessments will support: Risk distribution by system | Framework coverage dashboards | Gaps or missing documentation

Can AI Risk handle multiple systems or models at once?

Yes. Assessments are per system/model but the interface will support a portfolio-level view.

Is this built to scale with new regulations?

Yes. New frameworks, jurisdictions, or internal review processes can be added via configuration. We plan to provide prebuilt updates for major regulatory shifts post-GA.

How does AI Risk integrate with existing AI governance software?

Radar AI Risk connects seamlessly with other AI governance tools, enabling centralized oversight without the need to replace existing systems.

Can AI Risk support high level reporting for executives and boards?

Yes. The platform offers high level dashboards and scorecards designed for leadership to quickly assess organizational AI risk posture.

How does AI Risk help with training data compliance?

AI Risk tracks and documents training data quality, provenance, and use, ensuring compliance with privacy and ethical guidelines.

Is Radar AI Risk suitable for organizations just beginning to adopt AI?

Absolutely. Whether you are starting small or scaling enterprise-wide, Radar AI Risk provides the structure to manage compliance from the beginning of development and deployment.

Legal

Radar Privacy™ Onboarding Overview

Onboarding Overview – Radar Privacy™

The Radar Privacy™ onboarding process is initiated after contract signing. You will be assigned a dedicated RadarFirst Onboarding Manager who will share best practices and guide your team through each phase described below. Before your Radar Privacy™ kickoff call, identify your core onboarding team (we recommend 5 people or less) and your IT resources for the project.

The onboarding project has 3 primary areas of focus:

Identifying data needed for reporting and configuring Radar Privacy™ accordingly.
Providing administrators with the knowledge to manage Radar Privacy™.
Training administrators and users on the Radar Privacy™ workflow, correctly profiling incidents and understanding results of the multi-factor risk assessment.

Onboarding Phases

Plan

Your RadarFirst Onboarding Manager will schedule a kickoff call with your core onboarding team to discuss and outline the project timeline, establish go-live requirements, and identify the criteria for a successful onboarding. Documentation on single sign-on and the API (if applicable) will be provided. Future project meetings are scheduled during this kickoff call. RadarFirst provides early access to view your Radar Privacy™ account, which will provide visibility into the configurable sections and facilitate the subsequent configure phase of the project.

Configure

This phase focuses on identifying the data that matters most for reporting purposes and configuring those fields in Radar Privacy™. In addition to adjusting the default fields to capture needed information, your team will be able to identify any organization-specific data you want to gather via custom fields. Your Onboarding Manager will assist by comparing your current incident intake form(s) to the standard data fields in Radar Privacy™.

Weekly Meetings
During the weekly onboarding meetings, your Onboarding Manager will demonstrate how to configure key features of the system, providing guidance on how to best manage your organization’s specific needs and use cases in the Radar Privacy™ product. Weekly meetings are typically held at the same time on the same day of the week to establish consistency across teams. Onboarding Managers have pre-prepared topics and resources to assist customers through the configuration process of their new Radar Privacy™ product. However, at any time, users with Admin or Owner privileges can easily refine the data fields within your account based on ongoing internal feedback.

Configure Radar Privacy™
Your Radar Privacy™ account is ready to perform incident assessments as soon as you receive access, but can be configured to better align with your business needs. The timeframe for the configuration phase of onboarding is based on the average length of onboarding. Customers that choose to configure more areas of their account often need a longer configuration phase. Examples of areas of the Radar Privacy™ account that can be configured include: custom fields, data elements, risk factor scenarios, notification letters, incident groups, and departments.

Configure Submission Form
Your Onboarding Manager will assist your team with configuring your submission forms. Prior to using Radar Privacy™, many customers collect incident information via hotlines, internal forms, spreadsheets, and emails. Through submission forms, customers are able to train teams to report incidents in a standardized way, allowing incident response teams to collect incident-specific data in one location for accurate and efficient incident processing. In this phase, your Onboarding Manager will ask you to share any existing intake forms, mapping fields in your form to existing fields in Radar Privacy™, and configure custom fields.

Determine Reporting Criteria
The core onboarding team will learn how to create and run reports based on the needs your team has identified. Your Onboarding Manager can help you map any existing reports to your Radar Privacy™ account. It is possible to include custom data fields in our standardized reports.

IT Projects
As needed, configuration of Single Sign-on (SSO), Application Programming Interface (API), or other technical components and integrations will be conducted in this phase.

Train

Your RadarFirst Onboarding Manager will conduct training sessions based on your incident management processes and from within your configured Radar account. An optional Admin review conducted at the end of onboarding will provide an end-to-end recap of administrative configuration options, reporting capabilities, and support resources. User Training focuses on the incident workflow: correctly profiling an incident, understanding the risk assessment, and reviewing related decision support and reporting. To support this phase, we suggest providing RadarFirst with three to five common incident scenarios that are realistic examples for your organization.

Launch

After Radar Privacy™ is configured and the training phase is complete, you will be ready for launch! In this phase, your Onboarding Manager will be available to assist with additional questions as you communicate with internal groups about next steps. This is the much-anticipated day that your team has been working diligently toward. Congratulations! You have achieved a major milestone! At Launch, your Radar Privacy™ onboarding project will be complete. A half-hour call will take place to wrap up the project and transition your point of contact from an Onboarding Manager to a Customer Success Specialist.

Refine

Your team will move to active customer status and begin to receive RadarReport communications, quarterly update emails from the Customer Success team, invitations to webinars, and roadmap updates directly from the Product Management team. Your Customer Success Specialist will work with your team to expand Radar usage at your company, schedule feature demos, and help you connect with training resources.

Day-to-day questions will be addressed within the Radar Privacy™ Help Center or by our expert Product Support team. Our Help Center provides 24x7x365 access to step-by-step instructions and concise video tutorials. Our Product Support team will also be available to assist with continuous refinement of the configuration options and to address any technical issues.