Overview
Policy Statement
This policy describes the requirements and implemented controls for managing Data.
Any person who creates, uses, stores, or transmits your organization Data, and called hereafter Data Owner, has the responsibility to maintain and safeguard such Data. The very first step is to determine the level of sensitivity applicable to such Data and classify it. This step is handled by the Data Owner.
According to some regulations, such as the HIPAA Rules, covered entities "must securely back up retrievable exact copies of protected health information" and must be able to fully "restore any loss of data". Furthermore, additional security rules mandate that the backup should be frequent, encrypted, tested, and stored offsite.
Complete backups of both your organization and your organization's customers' Protected and Confidential Data is performed daily and by respecting the 3-2-1 Backup Rule: "keep at least three (3) copies of your data, and store two (2) backup copies on different storage media, with one (1) of them located offsite".
Scope
This policy applies to all Information Systems and Information Resources owned or operated by or on behalf of your organization. It can be used for any data that are stored, processed, or transmitted by your organization, including but not limited to:
- Electronic data;
- Data recorded on paper;
- Information shared orally, visually, or by other means.
Procedures
Procedures and mapped controls
Data Lifecycle Management
your organization is primarily a Cloud Computing company and the digital information it possesses from operations, internal infrastructure, and customers are hosted on Cloud Computing infrastructure and storage.
your organization uses different stages for :
- Development
- Testing
- Production
In all stages, Digital Information (Data) will be stored, retrieved, archived, or deleted regularly, depending on the operations required to make use of it.
your organization operates under the principle of "C, I, A – Confidentiality, Integrity, and Availability" of the data, a principle that applies to all handled digital information as well.
All digital information and associated operations available for it are governed by the rules outlined in the Data Handling Procedure and at no time a single entity is granted full access and rights to it.
For all the following processes your organization has implemented controls, guidelines, and worksheets to keep track of access times, categorize the collected digital information and log all performed actions.
Data Classification
This procedure is intended to help your organization employees and 3rd Parties classify data to determine its need for protection, handling, and determining applicable policies and laws.
Depending on the regulatory compliance Standards your organization has to comply with, the following levels of data classification are defined:
- Protected Data
- Confidential Data
- Internal Data
- Public Data
Protected Data
Protected data refers to any information protected by federal, state, or local laws and regulations or industry standards, such as HIPAA, HITECH, GDPR, the New York State Information Security Breach and Notification Act, similar state laws, and PCI-DSS.
Unauthorized disclosure of Protected data will cause major problems to business operations, generate a significant cost, damage the company's reputation, and can result in legal prosecution for your organization.
Protected data requires privacy and security protections. Special authorization is required for use and collection, and the disclosure of this class of data is prohibited without prior approval.
Characteristics of Protected Data
- Protected Data cannot be stored outside properly protected and labeled environments.
- Protected Data must be encrypted at all times, both at rest and in transit.
- CISO Approval: when a business need arises, the CISO must authorize all storing, processing, and transmitting of Protected Data.
- Compliance Risk: Protection of information is mandated by law (HIPAA, GDPR, GLBA, CCPA) or required by private contract (PCI DSS).
- Reputation Risk: Loss of confidentiality or integrity will cause significant damage to your organization's reputation.
- Other Risks: Loss of the confidentiality or integrity of the information that could cause harm to individuals and cause the company to incur significant costs in response.
Examples of Protected Data
- PII, such as Social Security Numbers (SSN) or last four numbers of an individual's SSN
- Personal Data for an EU Citizen - governed under GDPR
- PHI (Protected health information) or ePHI - governed under HIPAA/HITECH
- CHD (Payment card cardholder data) - governed under PCI-DSS/PA-DSS
- Credit/debit card numbers, bank account, financial information
- Production Secrets, Passwords, and Encryption keys
Confidential Data
This type of data is restricted information that is required to be maintained in a highly confidential manner as directed by your organization's Privacy Officer, applicable law or regulation, contractual obligation, or subject to any applicable legal privilege or protection.
Unauthorized disclosure of Confidential data will cause business operations problems and some financial loss.
Characteristics of Protected Data
- Access to Confidential Data is limited to your organization employees and 3rd Parties operating under an executed non-disclosure agreement. This information should never be stored on a computing device or electronic storage media that is personally owned unless expressly permitted.
- Protected Data must be encrypted at all times, both at rest and in transit.
- Compliance Risk: Protection of data is mandated by law (e.g. FERPA) or required by private contract (e.g. non-disclosure agreements).
- Reputation Risk: Loss of confidentiality or integrity will cause significant damage to your organization's reputation. For example, loss of social security numbers or defacement of the your organization website would likely be a news item that would appear in the media.
- Other Risks: Loss of confidentiality that could cause harm to individuals such as your organization personnel, and partners. Loss of confidentiality or integrity would cause your organization to incur significant costs in response.
- Treatment in Open Records Requests: Sensitive information is typically redacted from open records disclosures.
Examples of Confidential Data
- Business-critical intellectual property, proprietary data, and/or trade secrets, business plans
- IP-rich Source Code, Business Application Source Code
- HR records (e.g., background check reports, salary, DoB, employment records, etc.)
- Non-public tax and accounting data
- Non-production Secrets, Passwords, and Encryption keys
- Network and infrastructure designs
- Customer lists and contacts
- Security, system, and application audit logs
- Internal information security protocols, plans, and processes
Internal Data
Any information that is proprietary or produced only for internal use in your organization.
Unauthorized disclosure of Protected data may result in major disruption to business operations, significant cost, irreparable reputation damage, and/or legal prosecution for your organization.
Protected data requires privacy and security protections. Special authorization is required for use and collection, and the disclosure of this class of data is prohibited without prior approval.
Examples of Internal Data
- Application data that does not fall into Protected or Confidential levels
- Product details and roadmaps, which will be made public at some point
- Internal operating procedures and operational manuals, security policies and procedures
- Internal memoranda, emails, reports, communications (e.g., Teams, Slack, Zoom), and other documents
- IP addresses, system names, account names
- Source code that is not business critical or contains little or no IP
Public Data
This type of information can be disclosed without any restriction at any given time and by any your organization employee or 3rd Party. This type of data has no legal restrictions on its access or use.
Examples of Public Data
- Any information made available on the company's website and subdomains such as
support, help, blog, etc. - Financial statements and other reports filed for tax purposes and generally available to the public
- Marketing information that is part of materials or posted on Social media
Data Handling
Information assets shall be handled according to their prescribed classification, including access controls, labeling, retention policies, and destruction methods, among others.
In general, controls assigned by Data Asset Owners will deal with the confidentiality category of the data. The categories representing Integrity and Availability will be used to guide your organization to protect against the loss or corruption of the data.
| Data | Retention¹| Labeling | Non-prod storage | Encrypt (rest, transit) | Access Control²| Backup | |-----------------|-----------|----------|------------------|-------------------------|----------------|------------| | Protected | 5 yrs | Yes | No | Yes, Yes | Yes | Required | | Confidential| 3 yrs | Yes | Yes | Yes, Yes | Yes | Required | | Internal | Optional | Yes | Yes | No, Yes | No | Optional | | Public | Optional | Optional | Yes | No, No | Now | Optional |
¹There are situations when data retention may differ, depending on business needs and regulatory requirements.
²The need-to-know requires that Data Assets should only be available to those who need to use or access the Data Asset to do their work.
Mapped controls
Ensure management ports are restricted from the internet
Ensure all S3 buckets employ encryption-at-rest
Ensure S3 Bucket Policy is set to deny HTTP requests
Ensure EBS encryption by default is enabled
Ensure no Network ACLs allow ingress from 0.0.0.0/0 to remote server administration ports
Ensure management ports are restricted from the internet
Ensure user-managed/external keys for service accounts are rotated every 90 days or less
Ensure that Separation of duties is enforced while assigning KMS related roles to users
Ensure that object versioning is enabled on log-buckets
Ensure the default network does not exist in a project
Ensure Separation of duties is enforced while assigning Service Account related roles to users
Ensure RSASHA1 is not used for the key-signing key in Cloud DNS DNSSEC
Ensure RSASHA1 is not used for the zone-signing key in Cloud DNS DNSSEC
Ensure Cloud Storage buckets have uniform bucket-level access enabled
Data Deletion
There are times when digital information must be destroyed entirely for several reasons:
- your organization stores digital information for 3 years either in the original form or archived; After this period and if no further contractual obligations have to be met, data will be destroyed by deletion; As your organization is using Cloud Storage, it initiates the procedure of deletion based on the instructions from the Cloud Provider and logs the operations for later reference;
- If a customer is requesting deletion of data, this must be carried out by following GDPR, CCPA or HIPAA, and performed in a timely interval. your organization will delete data requested by customers in 90 days from the request being formally sent;
- Personal data was unlawfully processed;
- Data is no longer relevant or provides no meaningful insights;
- Data has expired in the lifecycle based on an agreement;
- Regulatory compliance – where applicable;
Active customers' data is preserved for as long as the customer is active. Unless otherwise stated or data belonging to inactive customers is not part of an investigation, the inactive account will have its data automatically removed within 30 days.
Free or Trial customers that wish to voluntarily close their account should download their data manually or via the API before closing their account. After the trial period has expired, customers in this category will have their data deleted automatically from the systems within 7 days.
Data Wiping
All company-owned devices are subject to a complete data wipe. In the event of the device being lost or stolen, the owner must inform the IT Team as soon as possible, giving details of the circumstances of the loss and the sensitivity of the business information stored on it. your organization reserves the right to remote wipe the device where possible as a security precaution. This may involve the deletion of non-business data belonging to the device owner.
Query logic
These are the stored checks tied to this policy.
Security Groups with management ports not restricted from the internet
Connectors
Covered asset types
Expected check: eq []
{
securityGroups(
where: {
rules_SOME: {
direction: "Inbound"
action: "Allow"
AND: [
{
OR: [
{ sources_INCLUDES: "cidr:0.0.0.0/0" }
{ sources_INCLUDES: "cidr:::/0" }
{ sources_INCLUDES: "tag:Internet" }
{ sources: [] }
]
}
{
OR: [
{ destFromPort_LTE: 22, destToPort_GTE: 22 }
{ destFromPort_LTE: 3389, destToPort_GTE: 3389 }
]
}
]
}
}
) {
...AssetFragment
}
}Firewalls with management ports not restricted from the internet
Connectors
Covered asset types
Expected check: eq []
{
firewalls(
where: {
rules_SOME: {
direction: "Inbound"
AND: [
{
OR: [
{ sources_INCLUDES: "cidr:0.0.0.0/0" }
{ sources_INCLUDES: "cidr:::/0" }
{ sources: [] }
]
}
{
OR: [
{ destFromPort_LTE: 22, destToPort_GTE: 22 }
{ destFromPort_LTE: 3389, destToPort_GTE: 3389 }
]
}
]
}
}
) {
...AssetFragment
}
}
All S3 buckets employ encryption-at-rest
Connectors
Covered asset types
Expected check: eq []
buckets(where: { encrypted: false}) {...AssetFragment}S3 Bucket Policy is set to deny HTTP requests
Connectors
Covered asset types
Expected check: eq []
buckets(where: {OR: [{policyDocument_MATCHES: "^((?!(?i)\"effect\":\"deny\").)*$"},{policyDocument_MATCHES: "^((?!(?i)\"Bool|aws:SecureTransport|false\").)*$"}]}) {...AssetFragment}EBS encryption by default is enabled
Connectors
Covered asset types
Expected check: eq []
{ebsSettings(where: { encryptedByDefault: false }) {...AssetFragment}}No Network ACLs allow ingress from 0.0.0.0/0 to remote server administration ports
Connectors
Covered asset types
Expected check: eq []
networkAcls(where:{rules_SOME:{AND:[{direction:"Inbound"},{action:"Allow"},{OR:[{sources_INCLUDES:"cidr:0.0.0.0/0"}, {sources_INCLUDES: "cidr:::/0"}]},{OR:[{destFromPort_LTE: 22, destToPort_GTE: 22}, {destFromPort_LTE: 3389, destToPort_GTE: 3389}]}]}}){...AssetFragment}User-managed/external keys for service accounts are rotated every 90 days or less
Connectors
Covered asset types
Expected check: eq []
GCPIAM5{...AssetFragment}Separation of duties is enforced while assigning KMS related roles to users
Connectors
Covered asset types
Expected check: eq []
{
iamUsers(
where: {
AND: [
{
hasIAMRole_SOME: {
OR: [
{ name: "roles/cloudkms.admin" }
{ name: "roles/owner" }
{ name: "roles/editor" }
]
}
}
{
hasIAMRole_SOME: {
OR: [
{ name: "roles/cloudkms.cryptoKeyEncrypterDecrypter" }
{ name: "roles/cloudkms.cryptoKeyEncrypter" }
{ name: "roles/cloudkms.cryptoKeyDecrypter" }
]
}
}
]
}
) {
...AssetFragment
}
}
Object versioning is enabled on log-buckets
Connectors
Covered asset types
Expected check: eq []
GCPLogging3{...AssetFragment}The default network does not exist in a project
Connectors
Covered asset types
Expected check: eq []
vpcs(where:{name:"default"}){...AssetFragment}Separation of duties is enforced while assigning service account related roles to users
Connectors
Covered asset types
Expected check: eq []
{
iamUsers(
where: {
AND: [
{
hasIAMRole_SOME: {
name: "roles/iam.serviceAccountAdmin"
}
}
{
hasIAMRole_SOME: {
name: "roles/iam.serviceAccountUser"
}
}
]
}
) {
...AssetFragment
}
}RSASHA1 is not used for the key-signing key in Cloud DNS DNSSEC
Connectors
Covered asset types
Expected check: eq []
managedZones(where:{hasDNSKeySpec_SOME:{keyType:"keySigning",algorithm_MATCHES:"(?i)rsasha1"}}){...AssetFragment}RSASHA1 is not used for the zone-signing key in Cloud DNS DNSSEC
Connectors
Covered asset types
Expected check: eq []
managedZones(where:{hasDNSKeySpec_SOME:{keyType:"zoneSigning",algorithm_MATCHES:"(?i)rsasha1"}}){...AssetFragment}Cloud Storage buckets have uniform bucket-level access enabled
Connectors
Covered asset types
Expected check: eq []
buckets(where:{iamConfigurationUniformBucketLevelAccessEnabled:false}){...AssetFragment}
Alibaba Cloud
AWS
Google Cloud
Microsoft Azure