# Ontology overview

Supported in:
The Google Security Operations ontology uses a formal specification that provides a
shareable and reusable knowledgeable representation of alerts and events. The ontology lets Google SecOps build entities from events and define relationships
between them. This process lets you see the full picture and explore potential threats on the
[Explore](https://docs.cloud.google.com/chronicle/docs/soar/investigate/working-with-cases/explore-entities-and-alerts-investigation) page. Once entities have been defined using the ontology, you can run
actions on them based on their role in the attack or event.

> [!NOTE]
> **Note:** Most integrations include a pre-configured ontology that provides a ready-made structure you can adapt or extend to meet your needs, instead of creating the entire structure manually.

## View the Ontology status

Go to **Settings \> Investigation \> Ontology Status** to see the following information:

- **Number of product types**: The number of products that Google SecOps captures from your environment. This number changes as more products are added to your environments.
- **Number of event types**: The number of events that Google SecOps captures.
- **Number of events assigned to default families** : The number of events that Google SecOps has automatically assigned. You can reassign an event (at any time) by locating the default value in the **Family Name** column and click settings **Configure**.

You can export selected ontology status rows as a ZIP file containing a JSON file. You can also import ontology status rows. Be sure to import a ZIP file that contains a JSON file with the ontology details.

## Set up model families

After you've established an initial data connection, you'll need to do the following:

1. Complete the following procedures to ensure that the data is ingested into the Google SecOps data model.
2. Map and model new events and alerts according to your requirements.

To set up a model family, follow these high-level steps:

1. Define the family: click **Settings \> Investigation \> Visual Families**.
2. Assign the family to the Event (or Product/Source) from either the [Alerts events](https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/ontology/deciding-what-events-to-configure) tab or the [Ontology status](https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/ontology/ontology-overview#ontology-status) page, click **Event Configuration \> Visualization**.

## Map data fields

To map data fields, follow these high-level steps:

1. On the **Case Management** or **Explore** page, correct any missing or incorrect field information.
2. Check if this can be solved by attaching a new Visual Family; otherwise, edit and configure the rules that make up both the family and the general system fields on the [Event Configuration \> Mapping page.](https://docs.cloud.google.com/chronicle/docs/soar/admin-tasks/ontology/configure-mapping-and-assign-visual-families)

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)