Skip to content

Control the AI you use

AI
Governance

We set up the policy, intake process and accountability for the AI you build and buy, mapped to the NIST AI RMF and ISO/IEC 42001. You learn what AI is already in use, who approves new uses, and what a project must show before it touches customer data or real decisions.

From inventory to operation

Every AI use
has an owner.

We follow the Govern function of the NIST AI RMF and build toward ISO/IEC 42001 if certification is on your roadmap. EU AI Act risk categories are mapped where they apply. Governance is sized to your organization, so approval stays quick for low risk uses.

Phase 01 · AI inventory

Find the AI already in use.

An inventory of AI tools, features and models in use, sanctioned or not.

  • Approved tools, embedded vendor AI and internal models listed.
  • Unsanctioned AI found through SSO, expense and network records.
  • The data each use touches recorded.

Phase 02 · Policy

Write rules people can follow.

An AI policy and acceptable use standard approved by leadership.

  • Acceptable use for staff, with data rules by classification.
  • Development standards for teams building with AI.
  • Prohibited and restricted uses stated plainly.

Phase 03 · Intake & review

Give new AI uses a clear path to approval.

An intake form and review process that scales review effort to risk.

  • Risk tiers for proposed uses, from internal drafting help to decisions about customers.
  • Security, privacy and legal review steps defined per tier.
  • AI questions added to your vendor review.

Phase 04 · Accountability

Name who owns each decision.

Roles, an AI review group and decision rights, recorded and agreed.

  • A business owner named for every AI system in production.
  • Review group membership and escalation path set.
  • Reporting to leadership and the board defined.

Phase 05 · Operate & hand off

Run the first reviews together, then hand over.

A working governance process with its first cases decided and recorded.

  • First intake reviews run alongside your team.
  • Steps that slowed approvals without reducing risk removed.
  • A gap list toward ISO/IEC 42001 delivered if you plan to certify.

Find the AI already in use.

An inventory of AI tools, features and models in use, sanctioned or not.

  • Approved tools, embedded vendor AI and internal models listed.
  • Unsanctioned AI found through SSO, expense and network records.
  • The data each use touches recorded.

Key benefits

Say yes to AI with the risks in view.

See the AI already in use

The inventory shows which AI tools and features your people use today and what data they touch. Governance starts from facts, not from a policy written for an imagined company.

Approvals that don't stall projects

Low risk uses move through a light review. High risk uses get the scrutiny they need. Teams know the path in advance, so they stop working around it.

Mapped to NIST and ISO

Policies and processes map to the NIST AI RMF and ISO/IEC 42001, so customers, regulators and auditors see a recognized structure behind your answers rather than a homegrown policy they have to decode.

What you get

What lands on
your desk.

Three handoffs that keep governance running after the engagement.

The document

The AI policy set

AI policy, acceptable use standard, development standard and the intake procedure, mapped to the NIST AI RMF and the ISO/IEC 42001 Annex A controls, and written in language staff can follow.

The working file

The AI register

Every AI use with its owner, risk tier, data touched, approval status and next review. Your governance group's record of what is approved and why.

The conversation

The governance launch

A working session with leadership and the new review group to walk through the policy, decide the first intake cases and confirm who owns what.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Governance questions

Asked before
the first policy.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Not always. Some customers and regulators have started to ask for it. We build to its structure either way, so certifying later is a step rather than a restart. Whether to certify is a business decision we can help you weigh.

It can apply to US organizations that place AI systems on the EU market or whose AI output is used in the EU. We map your uses against its risk categories, and your counsel confirms the legal position.

Badly designed governance does. Ours scales review effort to risk, so a team using an approved tool to draft documents moves quickly, while a model that makes credit decisions gets a full review.

Governance sets the policy, roles and approval path. AI Risk Management runs the risk register for the systems that pass through it. Governance usually comes first, and risk management follows as AI use grows.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.