Classification
Turn discovered data into clear classifications.
ClAIssify helps teams understand what their data contains and how it should be handled. It brings detected findings together by data type, location, and sensitivity tier, giving security, privacy, and compliance teams a clearer starting point for review.
Classification
What the latest scans found in your files and databases, sorted by how sensitive it is.
15,044 classified
4,088 Restricted or Highly Confidential
0 databases, 0 tables
0 columns classified
0 Restricted or Highly Confidential
0 with personal data
| Kind of data | Category | Files | Database columns | Stores |
|---|---|---|---|---|
| Payment card number Sensitive | Financial (PFI) | 659 | 3 | 18 |
| Medical licence (DEA) number Sensitive | Health (PHI) | 501 | 0 | 10 |
| Singapore NRIC or FIN Sensitive | Personal data (PII) | 400 | 0 | 12 |
Why classification matters
Finding sensitive data is only part of the job.
Teams also need to understand how sensitive it is so they can apply the right protections.
Without consistent classification, a personal identifier, a business document, and information approved for public use can appear alike in a large inventory. Clear sensitivity labels help teams decide what needs tighter access, closer review, or a different handling policy.
Classification gives teams a shared way to:
Prioritize protection: focus attention on data assigned to higher sensitivity tiers.
Apply policies consistently: use the same classification approach across connected stores.
Make reviews more useful: see the data type, sensitivity, and location together.
Support governance: use classified inventory to inform access reviews, remediation, and compliance work.
AI-assisted understanding
AI-assisted understanding, clear classification.
A value does not always explain itself. A sequence of digits, for example, could represent several different things depending on the surrounding content.
ClAIssify combines detection methods with AI-assisted context analysis to help interpret what a potential finding represents. Classification rules then map findings to your organization’s sensitivity tiers. This gives teams context for review while keeping the tiering process consistent with configured rules.
Applicant record
- Applicant ID
- value obscured
- Department
- HR
Finding
National identifier
Identity data · HR / Applicant record
Invoice archive
- Invoice reference
- value obscured
- Department
- Finance
Finding
Invoice reference
Business data · Finance / Invoice archive
How a finding is classified
From a finding to a sensitivity tier.
01
Detect a potential finding
ClAIssify scans supported files and records in connected sources for recognized data types.
02
Interpret it in context
AI-assisted analysis considers surrounding information to help distinguish between different kinds of data.
03
Apply classification rules
Configured rules map the finding to a sensitivity tier and relevant data category.
04
Review the result
Teams can see the classification alongside the finding’s type and location, then decide what follow-up is appropriate.
Classification tiers
Five tiers. One clearer view.
- Restricted
- The highest sensitivity tier. Use it for information that requires the strictest handling under your organization’s policy.
- Highly Confidential
- Sensitive information that should be limited to specifically authorized people or roles.
- Confidential
- Information that requires controlled access and should be handled according to internal policy.
- General
- Routine information intended for normal internal use.
- Public
- Information approved for public distribution.
Your organization’s policies determine which data belongs in each tier. ClAIssify’s configured rules should reflect those definitions.
- Restricted
- Highly Confidential
- Confidential
- General
- Public
Beyond the label
Make classification useful beyond the label.
A tier is most useful when teams can connect it to a next step. ClAIssify organizes findings so teams can review which data types were identified, where they were found, and how sensitive they are. That gives teams a more practical basis for deciding what to investigate, protect, or include in a governance workflow.
Know what the data represents. Understand its sensitivity. Make the next review clearer.