Skip to content

Know what data matters

Data Security
Governance

We set the rules that decide how your data is classified, who owns it, and how it may be stored, shared, kept and destroyed. You learn where sensitive data really lives, who answers for it, and which handling rules people can follow without stopping to read a policy.

Rules people can follow

Every dataset
has an owner.

The work draws on the data security category in NIST CSF 2.0, CIS Controls v8.1 Control 3 and the information classification controls in ISO/IEC 27001 Annex A. We keep the classification scheme short, because a scheme nobody remembers protects nothing.

What we examine

Data inventory

Find where sensitive data actually lives.

A data inventory naming each major data store, what it holds and who uses it.

  • Systems, file shares, SaaS apps and cloud storage reviewed with their owners.
  • Sensitive categories located: customer, employee, financial, health and regulated data.

Classification

Decide which data matters, and how much.

A classification scheme with few enough levels that staff apply it correctly.

  • Levels defined with plain examples from your own business.
  • Labels mapped to tools you already own, such as Microsoft Purview sensitivity labels.

Ownership

Give every dataset someone who answers for it.

A named owner and custodian for each data domain, agreed by leadership.

  • Data owners chosen from the business instead of defaulting to IT.
  • Owner duties written on a single page they will read.

Handling rules

Say what each class of data may do.

Handling rules covering storage, sharing, transfer and printing for each level.

  • Rules for email, file sharing, removable media and AI tools.
  • An exceptions process for teams with a real business need.

Retention & disposal

Keep what you must, and destroy the rest.

A retention schedule tied to legal and business need, with secure disposal steps.

  • Retention periods gathered with legal and records owners.
  • Disposal methods set for paper, devices and cloud data.
  • Stale data stores flagged for cleanup.

Access

Check that access follows the rules.

A view of where access to sensitive data is broader than its owner intended.

  • Access to the most sensitive stores sampled and compared to role.
  • Open shares and public links found in collaboration tools.

Key benefits

Protect the data that matters most.

Know where the data is

You get an inventory of where sensitive data lives and who touches it. Every later decision, from DLP rules to breach response, starts from that map.

Owners who answer for it

Each data domain gets a named business owner. Access questions, retention decisions and exceptions go to a person who can decide, instead of bouncing around IT.

Rules staff can follow

Classification uses a handful of levels with examples from your own work. Staff can label a document correctly in the moment, and IT can enforce the label.

What you get

What lands on
your desk.

Each handoff is something your team will use, not file away.

The document

The data governance standard

Classification levels, handling rules, ownership duties and the retention schedule in one short standard, written for staff and backed by detail for IT and legal.

The working file

The data inventory

Each data store with its classification, owner, location, retention period and access notes. The working record your team updates as systems are added, changed or retired.

The conversation

The data owner workshop

A working session with the new data owners to walk through their duties, confirm classifications and settle open questions before the standard is published to the rest of the organization.

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.

Data questions

Asked by
data owners.

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

No. We need to know where data lives and what it is, not to read it. Owners describe their systems, and where needed we review settings and access lists with read only permissions.

Privacy concerns personal data and the rights of the people it describes. Data security governance covers all sensitive data, including financials, designs and contracts. The inventory and ownership work feed both programs.

Usually not at first. Many organizations already own labeling and access tools, such as Microsoft Purview in Microsoft 365. We design rules for the tools you have and say plainly where a new one would earn its cost.

Leadership and the data owners, working from our recommendation. We bring a draft based on your data and obligations. They decide how much protection each level gets, because they carry the cost and the risk.

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.