Data Classification Policy: Mitt Arv Technologies Private LTD
Data Classification Policy: Mitt Arv Technologies Private LTD
Contents
1. Objective
2. Scope
3. Policy Statement
6. Non-Compliance
7. Responsibilities
8. Schedule
9. Version history
1. Objective
The Data Classification Policy provides a way to categorize any data processed by the Mitt Arv staff, software,
and systems. The purpose of this policy is to establish a framework for classifying data based on its sensitivity,
value, and criticality to the organization. By understanding the types of available data, their classification, and
access level, one shall be able to map the appropriate access or level of protection needed. This clarity
ensures that critical company data can be secured.
2. Scope
The Mitt Arv Data Classification Policy applies to all the data handled, managed, stored, or transmitted by Mitt
Arv and the Mitt Arv staff. Managers and information owners shall assign the appropriate classification as and
when required.
3. Policy Statement
Each individual at Mitt Arv shall be responsible for reviewing, adhering to, and handling data according to the
classification levels defined below. The Data Classification definitions below provide a list of various types of
data and their classification levels. In case of difficulty in identifying a specific data element or uncertainty
regarding the associated risk and appropriate classification and handling, individuals are encouraged to
contact Mitt Arv's Information Security Officer for guidance and assistance.
This data or information may be shared with any person, organization, or system regardless of their
relationship with Mitt Arv. This classification is not limited to data or information meant for public consumption
but also includes any data or information that requires no special handling or any kind of safeguarding from
disclosure. The distribution of such data does not expose Mitt Arv, its customers, or its partners to any harm.
Examples of Public Data include product blogs, company websites, press releases, marketing collaterals,
career pages, etc.
This data shall be accessible by all staff within Mitt Arv and may be required for the smooth operational
functioning of the organization. Such information shall not be made available to parties outside Mitt Arv but
Examples of Company Internal Data include Information Security Policies & Procedures, HR Policies, Leave
Policies & Holiday Lists, Operational Procedures, etc.
This data & information shall be accessible by pre-authorized staff members and shall not be made generally
available within Mitt Arv. Unauthorized access or disclosure could cause significant financial or material loss
and poses a risk to Mitt Arv if exposed. Such exposure can lead to breaking contractual obligations and may
adversely impact Mitt Arv, its partners, employees, and eventually its customers. Such information needs to be
protected from unauthorized access and changes. Note that access to such data may also be limited to
specific staff members or groups of staff members like executives, HR, legal teams, etc.
Examples of Company Confidential Data include employee salaries, legal documents, internal product
specifications, customer lists, strategy documents, internal roadmaps, design documents, internal memos,
emails, etc.
This data, if accessed by unauthorized parties, may adversely affect Mitt Arv’s customers. This includes data
that Mitt Arv is required to keep confidential, either by law or under a customer agreement. The company
needs to protect such information from unauthorized access and unauthorized modification. Customer
Confidential Data needs to be safeguarded when it is stored, processed, used, and transmitted.
Unauthorized access to such data can violate contractual confidentiality agreements with customers, cause a
security incident, or affect Mitt Arv’s customer and industry confidence.
Examples of Customer Confidential Data include data provided by customers by using our system, information
on customer accounts, personally identifiable information of customers (or customers’ customers), etc.
This data, if accessed by unauthorized parties, may adversely affect the privacy of individuals. Personal Data
refers to any data relating to an identifiable individual or person. This includes data Mitt Arv is required to
safeguard, either by law (GDPR for EU citizens’ data) or under a customer agreement. The company needs to
protect such information from unauthorized access and unauthorized modification. Personal Data needs to be
safeguarded when it is stored, processed, used, and transmitted.
Unauthorized access to such data may potentially violate the law, break contractual data protection
agreements with customers, cause a security incident, or affect Mitt Arv’s customer and industry confidence.
Examples of Personal Data include name, email, phone number, IP Address, political views of individuals,
cookies, Personal Health Records, Credit Card information, etc.
Note that personal health records, credit card information, and other sensitive personal data may be subject to
additional laws based on the location of the owner of such data. For example, HIPAA regulations shall apply to
US citizens' personal health information.
6. Non-Compliance
Compliance with this policy shall be verified through various methods, including but not limited to automated
reporting, audits, and feedback to the policy owner. Any staff member found to be in violation of this policy may
be subject to disciplinary action, up to and including termination of employment or contractual agreement. The
disciplinary action shall depend on the extent, intent, and repercussions of the specific violation.
7. Responsibilities
The Information Security Officer is responsible for approving and reviewing policy and related procedures.
Supporting functions, departments, and staff members shall be responsible for implementing the relevant
sections of the policy in their area of operation.
8. Schedule
This document shall be reviewed annually and whenever significant changes occur in the organization.
End of Data Classification Policy. For version history, please see the next page.
Version history
Version Log Date