create-filegrc 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +18 -0
- package/bin/create-filegrc.js +8 -0
- package/package.json +26 -0
- package/src/cli.js +64 -0
- package/src/defaults.js +1063 -0
- package/src/index.js +252 -0
- package/template/AGENTS.md +227 -0
- package/template/README.md +102 -0
- package/template/data/AGENTS.md +185 -0
- package/template/data/action-items/AGENTS.md +11 -0
- package/template/data/audit-populations/AGENTS.md +13 -0
- package/template/data/audits/AGENTS.md +21 -0
- package/template/data/documents/document-business-continuity-disaster-recovery.json +29 -0
- package/template/data/documents/document-business-continuity-disaster-recovery.md +190 -0
- package/template/data/documents/document-contractor-policy-acknowledgement.json +21 -0
- package/template/data/documents/document-contractor-policy-acknowledgement.md +24 -0
- package/template/data/documents/document-contractor-training-acknowledgement.json +22 -0
- package/template/data/documents/document-contractor-training-acknowledgement.md +20 -0
- package/template/data/documents/document-data-retention-schedule.json +25 -0
- package/template/data/documents/document-data-retention-schedule.md +33 -0
- package/template/data/documents/document-employee-handbook-acknowledgement.json +21 -0
- package/template/data/documents/document-employee-handbook-acknowledgement.md +19 -0
- package/template/data/documents/document-employee-policy-acknowledgement.json +21 -0
- package/template/data/documents/document-employee-policy-acknowledgement.md +24 -0
- package/template/data/documents/document-employee-training-acknowledgement.json +22 -0
- package/template/data/documents/document-employee-training-acknowledgement.md +20 -0
- package/template/data/documents/document-incident-response-plan.json +29 -0
- package/template/data/documents/document-incident-response-plan.md +136 -0
- package/template/data/documents/document-soc2-management-assertion.json +17 -0
- package/template/data/documents/document-soc2-management-assertion.md +24 -0
- package/template/data/documents/document-soc2-management-representation.json +17 -0
- package/template/data/documents/document-soc2-management-representation.md +20 -0
- package/template/data/documents/document-soc2-period-completeness.json +17 -0
- package/template/data/documents/document-soc2-period-completeness.md +32 -0
- package/template/data/documents/document-soc2-system-description.json +17 -0
- package/template/data/documents/document-soc2-system-description.md +65 -0
- package/template/data/evidence/AGENTS.md +30 -0
- package/template/data/obligation-events/AGENTS.md +18 -0
- package/template/data/obligations/AGENTS.md +11 -0
- package/template/data/people/person-independent-approver.json +10 -0
- package/template/data/people/person-policy-owner.json +10 -0
- package/template/data/policies/AGENTS.md +15 -0
- package/template/data/policies/policy-anti-bribery-corruption.json +25 -0
- package/template/data/policies/policy-anti-bribery-corruption.md +87 -0
- package/template/data/policies/policy-clear-desk-screen.json +24 -0
- package/template/data/policies/policy-clear-desk-screen.md +49 -0
- package/template/data/policies/policy-data-protection-handling.json +34 -0
- package/template/data/policies/policy-data-protection-handling.md +130 -0
- package/template/data/policies/policy-employee-handbook.json +31 -0
- package/template/data/policies/policy-employee-handbook.md +161 -0
- package/template/data/policies/policy-information-security.json +61 -0
- package/template/data/policies/policy-information-security.md +233 -0
- package/template/data/policies/policy-mobile-computing-communications.json +28 -0
- package/template/data/policies/policy-mobile-computing-communications.md +74 -0
- package/template/data/renderer.json +7 -0
- package/template/data/risk-assessments/AGENTS.md +16 -0
- package/template/data/systems/system-filegrc-program-repository.md +9 -0
- package/template/data/training/training-anti-bribery-high-risk-roles.json +17 -0
- package/template/data/training/training-anti-bribery-high-risk-roles.md +19 -0
- package/template/data/training/training-privileged-sensitive-roles.json +21 -0
- package/template/data/training/training-privileged-sensitive-roles.md +20 -0
- package/template/data/training/training-secure-development.json +20 -0
- package/template/data/training/training-secure-development.md +22 -0
- package/template/data/training/training-security-awareness.json +28 -0
- package/template/data/training/training-security-awareness.md +192 -0
- package/template/data/workspace.json +27 -0
- package/template/docs/filegrc-audit.png +0 -0
- package/template/docs/filegrc-home.png +0 -0
- package/template/gitignore +4 -0
- package/template/package.json +15 -0
- package/template-parameters.json +34 -0
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
# Anti-Bribery and Corruption Policy
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
{{company_name}} conducts business honestly and complies with applicable anti-bribery and anti-corruption laws. No business result justifies offering, requesting, accepting, or concealing an improper payment or benefit.
|
|
6
|
+
|
|
7
|
+
## Scope
|
|
8
|
+
|
|
9
|
+
This policy applies to employees, contractors, officers, directors, agents, consultants, and third parties acting for {{company_name}}.
|
|
10
|
+
|
|
11
|
+
## Prohibited conduct
|
|
12
|
+
|
|
13
|
+
Covered persons must not directly or indirectly:
|
|
14
|
+
|
|
15
|
+
- Offer, promise, authorize, give, request, or accept anything of value to improperly influence a decision.
|
|
16
|
+
- Reward someone for misusing a position of trust.
|
|
17
|
+
- Use a third party to do something this policy prohibits.
|
|
18
|
+
- Make facilitation or expediting payments, except when necessary to prevent an immediate threat to health or safety.
|
|
19
|
+
- Create false, incomplete, misleading, or undisclosed records.
|
|
20
|
+
- Retaliate against someone who raises a concern in good faith.
|
|
21
|
+
|
|
22
|
+
"Anything of value" includes money, gifts, meals, travel, entertainment, discounts, services, employment opportunities, charitable contributions, political contributions, and benefits provided to a recipient's family or associates.
|
|
23
|
+
|
|
24
|
+
## Government officials
|
|
25
|
+
|
|
26
|
+
Interactions with government officials require added care. The term includes elected and appointed officials, employees of government agencies or state-controlled entities, political candidates, public international organizations, and anyone acting in an official capacity.
|
|
27
|
+
|
|
28
|
+
No payment, gift, or benefit may be offered to a government official to obtain or retain business, avoid a requirement, influence an official act, or secure an improper advantage.
|
|
29
|
+
|
|
30
|
+
## Gifts, meals, travel, and entertainment
|
|
31
|
+
|
|
32
|
+
Business courtesies must:
|
|
33
|
+
|
|
34
|
+
- Have a legitimate business purpose.
|
|
35
|
+
- Be reasonable, infrequent, and appropriate to the circumstances.
|
|
36
|
+
- Comply with the recipient's rules and applicable law.
|
|
37
|
+
- Never consist of cash or a cash equivalent.
|
|
38
|
+
- Never be intended to influence a pending decision.
|
|
39
|
+
- Be recorded accurately when {{company_name}} pays for them.
|
|
40
|
+
|
|
41
|
+
The policy owner must approve any courtesy that could reasonably appear improper.
|
|
42
|
+
|
|
43
|
+
## Political and charitable contributions
|
|
44
|
+
|
|
45
|
+
Company funds, property, or services may not be used for political contributions without written approval from the policy owner and confirmation that the contribution is lawful.
|
|
46
|
+
|
|
47
|
+
Charitable contributions must have a documented charitable purpose and may not benefit a decision-maker personally or act as a substitute for an improper payment.
|
|
48
|
+
|
|
49
|
+
## Third parties
|
|
50
|
+
|
|
51
|
+
Before engaging an agent, consultant, reseller, or other intermediary who may interact with customers or officials on {{company_name}}'s behalf, the responsible owner must:
|
|
52
|
+
|
|
53
|
+
1. Perform risk-based due diligence.
|
|
54
|
+
2. Confirm the service and compensation are commercially reasonable.
|
|
55
|
+
3. Use a written agreement describing the service and requiring lawful conduct.
|
|
56
|
+
4. Approve and retain invoices and supporting records.
|
|
57
|
+
5. Monitor for unusual requests, payment methods, or relationships.
|
|
58
|
+
|
|
59
|
+
Warning signs must be resolved before engagement or payment. Examples include:
|
|
60
|
+
|
|
61
|
+
- A request for payment to an unrelated person, unusual account, or country unrelated to the work.
|
|
62
|
+
- Vague services, excessive commissions, or invoices that do not match the agreement.
|
|
63
|
+
- A close relationship with a government official or decision-maker.
|
|
64
|
+
- Refusal to complete due diligence or sign appropriate contract terms.
|
|
65
|
+
- A request to hide a person's identity, role, or the purpose of a transaction.
|
|
66
|
+
|
|
67
|
+
## Books and records
|
|
68
|
+
|
|
69
|
+
Transactions must be recorded promptly, accurately, and with enough detail to explain their purpose. Undisclosed accounts, false descriptions, fabricated invoices, and off-book transactions are prohibited.
|
|
70
|
+
|
|
71
|
+
## Reporting
|
|
72
|
+
|
|
73
|
+
Report questions, suspected violations, requests for improper payments, or inaccurate records to {{policy_owner_name}} at {{security_contact_email}}. Reports may be made without first notifying a manager.
|
|
74
|
+
|
|
75
|
+
{{company_name}} prohibits retaliation against anyone who reports a concern or participates in an investigation in good faith.
|
|
76
|
+
|
|
77
|
+
## Investigations and enforcement
|
|
78
|
+
|
|
79
|
+
{{company_name}} will review credible reports promptly and limit disclosure to people who need the information. Covered persons must preserve relevant records and cooperate honestly.
|
|
80
|
+
|
|
81
|
+
Violations may result in removal of authority, termination of a contract or employment relationship, recovery of funds, and referral to authorities when appropriate.
|
|
82
|
+
|
|
83
|
+
## Training and review
|
|
84
|
+
|
|
85
|
+
People in higher-risk roles complete assigned anti-bribery training within 30 days of starting those duties or changing into a covered role. Covered roles include work involving sales, procurement, payments, gifts or hospitality, government interaction, higher-risk locations, or third parties acting for {{company_name}}. The onboarding or role-change checklist records the training assignment or why it does not apply.
|
|
86
|
+
|
|
87
|
+
This policy is reviewed at least annually and after a material legal, geographic, or business change.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": 1,
|
|
3
|
+
"id": "policy-clear-desk-screen",
|
|
4
|
+
"type": "policy",
|
|
5
|
+
"title": "Clear Desk and Clear Screen Policy",
|
|
6
|
+
"status": "draft",
|
|
7
|
+
"ownerIds": ["person-policy-owner"],
|
|
8
|
+
"approverIds": ["person-independent-approver"],
|
|
9
|
+
"policyKind": "information-security",
|
|
10
|
+
"version": "1.0",
|
|
11
|
+
"effectiveOn": "{{effective_date}}",
|
|
12
|
+
"reviewCadence": {
|
|
13
|
+
"mode": "calendar",
|
|
14
|
+
"unit": "year",
|
|
15
|
+
"interval": 1,
|
|
16
|
+
"anchorDate": "{{effective_date}}"
|
|
17
|
+
},
|
|
18
|
+
"audience": ["employees", "contractors"],
|
|
19
|
+
"acknowledgementRequired": true,
|
|
20
|
+
"controlIds": [
|
|
21
|
+
"control-policy-management",
|
|
22
|
+
"control-physical-workspace-security"
|
|
23
|
+
]
|
|
24
|
+
}
|
|
@@ -0,0 +1,49 @@
|
|
|
1
|
+
# Clear Desk and Clear Screen Policy
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
{{company_name}} protects confidential information from accidental exposure, theft, and unauthorized access in offices, shared spaces, and remote work locations.
|
|
6
|
+
|
|
7
|
+
## Scope
|
|
8
|
+
|
|
9
|
+
This policy applies to employees and contractors who handle company, customer, workforce, or vendor information.
|
|
10
|
+
|
|
11
|
+
## Clear desk requirements
|
|
12
|
+
|
|
13
|
+
When a workspace is unattended:
|
|
14
|
+
|
|
15
|
+
- Store confidential papers and removable media in a locked or access-controlled location.
|
|
16
|
+
- Remove passwords, access codes, keys, badges, and authentication devices from view.
|
|
17
|
+
- Do not leave payment information, identity documents, contracts, customer lists, or personnel records exposed.
|
|
18
|
+
- Retrieve sensitive print jobs immediately.
|
|
19
|
+
- Dispose of sensitive paper in an approved secure-destruction container.
|
|
20
|
+
- Return shared meeting rooms and work areas to a clean state.
|
|
21
|
+
- Secure portable equipment with a physical lock or security cable where practical.
|
|
22
|
+
|
|
23
|
+
At the end of the workday, secure confidential material and company equipment.
|
|
24
|
+
|
|
25
|
+
## Clear screen requirements
|
|
26
|
+
|
|
27
|
+
- Lock the screen whenever leaving a device unattended.
|
|
28
|
+
- Configure automatic screen locking after no more than 15 minutes of inactivity.
|
|
29
|
+
- Position screens to reduce unnecessary viewing by visitors or the public.
|
|
30
|
+
- Use a privacy screen when confidential information must be viewed in a public or shared location.
|
|
31
|
+
- Close files and applications that are no longer needed.
|
|
32
|
+
- Do not display passwords, secrets, or recovery codes on monitors or notes.
|
|
33
|
+
- Do not leave sensitive files, shortcuts, diagrams, or other information exposed on a shared desktop or display.
|
|
34
|
+
|
|
35
|
+
## Remote work
|
|
36
|
+
|
|
37
|
+
Remote workers must choose a workspace where household members, visitors, and the public cannot casually view or access confidential information. Voice and video calls involving confidential matters must be conducted where they cannot be overheard.
|
|
38
|
+
|
|
39
|
+
## Visitors
|
|
40
|
+
|
|
41
|
+
Visitors must remain in authorized areas and be supervised where confidential information or systems are present. Hosts are responsible for clearing exposed information before a visitor arrives.
|
|
42
|
+
|
|
43
|
+
## Lost material or suspected exposure
|
|
44
|
+
|
|
45
|
+
Report lost papers, devices, badges, removable media, or suspected unauthorized viewing immediately to {{policy_owner_name}} at {{security_contact_email}}.
|
|
46
|
+
|
|
47
|
+
## Enforcement and review
|
|
48
|
+
|
|
49
|
+
Failure to follow this policy may lead to access restrictions or disciplinary action. The policy owner reviews this policy at least annually.
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": 1,
|
|
3
|
+
"id": "policy-data-protection-handling",
|
|
4
|
+
"type": "policy",
|
|
5
|
+
"title": "Data Protection and Handling Policy",
|
|
6
|
+
"status": "draft",
|
|
7
|
+
"ownerIds": ["person-policy-owner"],
|
|
8
|
+
"approverIds": ["person-independent-approver"],
|
|
9
|
+
"policyKind": "information-security",
|
|
10
|
+
"version": "1.0",
|
|
11
|
+
"effectiveOn": "{{effective_date}}",
|
|
12
|
+
"reviewCadence": {
|
|
13
|
+
"mode": "calendar",
|
|
14
|
+
"unit": "year",
|
|
15
|
+
"interval": 1,
|
|
16
|
+
"anchorDate": "{{effective_date}}"
|
|
17
|
+
},
|
|
18
|
+
"audience": ["employees", "contractors", "vendors"],
|
|
19
|
+
"acknowledgementRequired": true,
|
|
20
|
+
"relatedDocumentIds": ["document-data-retention-schedule"],
|
|
21
|
+
"controlIds": [
|
|
22
|
+
"control-policy-management",
|
|
23
|
+
"control-risk-assessment",
|
|
24
|
+
"control-access-authorization",
|
|
25
|
+
"control-access-review-offboarding",
|
|
26
|
+
"control-data-classification-inventory",
|
|
27
|
+
"control-encryption-transmission",
|
|
28
|
+
"control-data-retention-disposal",
|
|
29
|
+
"control-incident-response",
|
|
30
|
+
"control-vendor-due-diligence",
|
|
31
|
+
"control-vendor-monitoring",
|
|
32
|
+
"control-security-exceptions"
|
|
33
|
+
]
|
|
34
|
+
}
|
|
@@ -0,0 +1,130 @@
|
|
|
1
|
+
# Data Protection and Handling Policy
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
This policy defines how {{company_name}} classifies, accesses, uses, stores, shares, retains, and disposes of data.
|
|
6
|
+
|
|
7
|
+
## Scope
|
|
8
|
+
|
|
9
|
+
This policy applies to employees, contractors, vendors, systems, devices, and records that create, receive, process, store, or transmit data on behalf of {{company_name}}.
|
|
10
|
+
|
|
11
|
+
## Responsibilities
|
|
12
|
+
|
|
13
|
+
{{policy_owner_name}} owns this policy. System and data owners decide which data a system may process, assign classifications, approve access, and set retention requirements. Everyone in scope must handle data according to its classification and report suspected loss or misuse.
|
|
14
|
+
|
|
15
|
+
Questions and reports should be sent to {{security_contact_email}}.
|
|
16
|
+
|
|
17
|
+
## Data classification
|
|
18
|
+
|
|
19
|
+
Data owners assign the highest classification required by the data in a record, file, system, or transfer.
|
|
20
|
+
|
|
21
|
+
| Classification | Description | Examples | Minimum handling |
|
|
22
|
+
| --- | --- | --- | --- |
|
|
23
|
+
| Public | Approved for public release | Published web content and public documentation | Protect integrity and use approved publishing processes |
|
|
24
|
+
| Internal | Intended for the workforce and approved partners | Internal procedures and routine business records | Limit access to people with a business need |
|
|
25
|
+
| Confidential | Disclosure could harm {{company_name}}, a customer, or another person | Contracts, financial records, customer data, source code, and security records | Approved systems, access control, encryption in transit and at rest, and protected sharing |
|
|
26
|
+
| Restricted | Disclosure or alteration could cause severe harm or trigger legal duties | Credentials, cryptographic keys, regulated data, and highly sensitive security material | Explicit approval, least privilege, encryption in transit and at rest, and additional monitoring |
|
|
27
|
+
|
|
28
|
+
When classification is uncertain, treat the data as Confidential until its owner decides.
|
|
29
|
+
|
|
30
|
+
Credentials, private keys, authentication tokens, and recovery codes must be stored in an approved secrets-management system. Do not put them in source files, tickets, chat messages, policy records, or other general-purpose repositories.
|
|
31
|
+
|
|
32
|
+
## Data inventory and ownership
|
|
33
|
+
|
|
34
|
+
{{company_name}} maintains records of systems and important data stores. Those records identify:
|
|
35
|
+
|
|
36
|
+
- An accountable owner
|
|
37
|
+
- Business purpose
|
|
38
|
+
- Data types and classification
|
|
39
|
+
- Source and authorized recipients
|
|
40
|
+
- Retention or deletion requirements
|
|
41
|
+
- Important vendors and processing locations
|
|
42
|
+
- Security and recovery needs
|
|
43
|
+
|
|
44
|
+
Owners review their records at least annually and after a material change.
|
|
45
|
+
|
|
46
|
+
## Collection and use
|
|
47
|
+
|
|
48
|
+
Collect only data needed for an approved business purpose. Tell people how their personal data will be used when required. Do not reuse data for an incompatible purpose without review and approval.
|
|
49
|
+
|
|
50
|
+
Access must follow least privilege. Owners approve access based on job duties, and managers or system owners review access at least quarterly for systems containing Restricted data and at least annually for other important systems.
|
|
51
|
+
|
|
52
|
+
Do not browse, copy, export, or analyze data out of curiosity or for personal use.
|
|
53
|
+
|
|
54
|
+
## Access approval and removal
|
|
55
|
+
|
|
56
|
+
Access to Confidential or Restricted data follows this process:
|
|
57
|
+
|
|
58
|
+
1. A manager or data owner requests access for a stated role and business need.
|
|
59
|
+
2. The reviewer checks that the requested access is the minimum needed.
|
|
60
|
+
3. The system owner or security owner approves elevated or sensitive access.
|
|
61
|
+
4. An authorized administrator provisions the access and records the decision.
|
|
62
|
+
5. Access changes and removals follow the same approval and recording requirements. Departures and role changes are handled promptly under the Information Security Policy.
|
|
63
|
+
|
|
64
|
+
## Storage
|
|
65
|
+
|
|
66
|
+
Internal, Confidential, and Restricted data must be stored in services approved for its classification. Local storage should be limited to a business need.
|
|
67
|
+
|
|
68
|
+
Confidential and Restricted data must be encrypted in transit over untrusted networks and at rest in approved systems and on devices. Encryption keys and data must have separate access controls where practical.
|
|
69
|
+
|
|
70
|
+
Production data must not be copied into development or test systems unless the owner approves the use and those systems meet the same protection requirements. Prefer generated or de-identified test data.
|
|
71
|
+
|
|
72
|
+
Paper records containing Confidential or Restricted data must be secured when unattended and destroyed with an approved method.
|
|
73
|
+
|
|
74
|
+
## Sharing and transfer
|
|
75
|
+
|
|
76
|
+
Before sharing Confidential or Restricted data, verify:
|
|
77
|
+
|
|
78
|
+
- The recipient and business need
|
|
79
|
+
- The minimum data required
|
|
80
|
+
- The recipient's authorization
|
|
81
|
+
- The transfer method and destination
|
|
82
|
+
- Contractual, privacy, and geographic restrictions
|
|
83
|
+
|
|
84
|
+
Use approved encrypted channels. Do not send Restricted data through personal email, consumer file-sharing accounts, or unapproved messaging services.
|
|
85
|
+
|
|
86
|
+
Public links must not be used for Confidential or Restricted data. Time-limit external access where the system supports it, and remove access when the business need ends.
|
|
87
|
+
|
|
88
|
+
## Vendors and subprocessors
|
|
89
|
+
|
|
90
|
+
Vendors that process Confidential or Restricted data must complete a security and privacy review before access begins. Contracts must state the permitted use, protection, incident notification, return or deletion, and any required audit rights.
|
|
91
|
+
|
|
92
|
+
Owners review critical vendors at least annually and when the service or data use changes materially.
|
|
93
|
+
|
|
94
|
+
## Retention and disposal
|
|
95
|
+
|
|
96
|
+
Keep data only as long as required for its business purpose and applicable legal, contractual, tax, audit, or security needs. Data owners document retention rules for important record classes in the Data Retention Schedule.
|
|
97
|
+
|
|
98
|
+
When retention ends, delete or anonymize the data through an approved process. Approved methods include cryptographic erase or secure wiping for reusable media and physical destruction, pulverization, or shredding for media that will not be reused. Choose a method suited to the medium and data classification.
|
|
99
|
+
|
|
100
|
+
Disposal must cover active systems, local copies, and vendor-held data where practical. Backup copies may expire through the normal protected backup cycle if they cannot be selectively deleted.
|
|
101
|
+
|
|
102
|
+
Legal holds and active investigations suspend normal deletion for the affected data.
|
|
103
|
+
|
|
104
|
+
The policy owner reviews the Data Retention Schedule at least annually and within 30 days after a material change to systems, data use, vendors, contracts, or applicable duties. The schedule's approver must be separate from its owner.
|
|
105
|
+
|
|
106
|
+
## Personal data requests
|
|
107
|
+
|
|
108
|
+
Requests to access, correct, export, restrict, or delete personal data must be sent to the responsible privacy or legal owner. Track the request using the minimum personal data needed. This repository should use an opaque case ID and an approved-system reference when keeping the person's identity in Git would conflict with deletion duties.
|
|
109
|
+
|
|
110
|
+
## Security incidents
|
|
111
|
+
|
|
112
|
+
Report suspected loss, unauthorized access, unintended disclosure, or improper disposal immediately to {{security_contact_email}}. Do not delete evidence, contact affected people, or make external statements unless the incident lead authorizes it.
|
|
113
|
+
|
|
114
|
+
{{company_name}} will investigate, contain, document, and notify affected parties as required by its incident process and applicable obligations.
|
|
115
|
+
|
|
116
|
+
## Training and compliance
|
|
117
|
+
|
|
118
|
+
Workers receive data-handling training when they join and at least annually. Additional training may be required for people who handle Restricted data.
|
|
119
|
+
|
|
120
|
+
People who develop or materially change applications complete secure-development training within 30 days of starting those duties or changing into a covered role. Training covers common application risks, access control, input handling, secrets, logging, dependencies, and secure review.
|
|
121
|
+
|
|
122
|
+
Violations may result in access removal, corrective action, contract remedies, or other action allowed by law and agreement.
|
|
123
|
+
|
|
124
|
+
Exceptions require a documented business reason, owner, risk assessment, compensating controls, expiration date, and approval from {{policy_owner_name}}.
|
|
125
|
+
|
|
126
|
+
## Review
|
|
127
|
+
|
|
128
|
+
{{company_name}} assesses data-protection risks at least annually, either as part of the information security risk assessment or as a separate assessment. The assessment covers material changes in data use, systems, vendors, contracts, and applicable duties.
|
|
129
|
+
|
|
130
|
+
The policy owner reviews this policy at least annually and after a material change to data use, law, contracts, or systems. Git history records approvals and changes.
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": 1,
|
|
3
|
+
"id": "policy-employee-handbook",
|
|
4
|
+
"type": "policy",
|
|
5
|
+
"title": "Employee Handbook",
|
|
6
|
+
"status": "draft",
|
|
7
|
+
"ownerIds": ["person-policy-owner"],
|
|
8
|
+
"approverIds": ["person-independent-approver"],
|
|
9
|
+
"policyKind": "workforce-conduct",
|
|
10
|
+
"version": "1.0",
|
|
11
|
+
"effectiveOn": "{{effective_date}}",
|
|
12
|
+
"reviewCadence": {
|
|
13
|
+
"mode": "calendar",
|
|
14
|
+
"unit": "year",
|
|
15
|
+
"interval": 1,
|
|
16
|
+
"anchorDate": "{{effective_date}}"
|
|
17
|
+
},
|
|
18
|
+
"audience": ["employees"],
|
|
19
|
+
"acknowledgementRequired": true,
|
|
20
|
+
"controlIds": [
|
|
21
|
+
"control-security-governance",
|
|
22
|
+
"control-policy-management",
|
|
23
|
+
"control-security-communication",
|
|
24
|
+
"control-workforce-expectations",
|
|
25
|
+
"control-performance-review"
|
|
26
|
+
],
|
|
27
|
+
"relatedDocumentIds": [
|
|
28
|
+
"document-employee-handbook-acknowledgement",
|
|
29
|
+
"document-employee-policy-acknowledgement"
|
|
30
|
+
]
|
|
31
|
+
}
|
|
@@ -0,0 +1,161 @@
|
|
|
1
|
+
# Employee Handbook
|
|
2
|
+
|
|
3
|
+
## Purpose and status
|
|
4
|
+
|
|
5
|
+
This optional handbook template sets a common baseline for employment practices, workplace conduct, information security, and use of {{company_name}} resources. An employee handbook is not required for SOC 2.
|
|
6
|
+
|
|
7
|
+
It is not an employment contract or legal advice. It does not promise employment for a fixed term or change any written employment agreement. Local law, written employment terms, benefit plans, and approved regional supplements control when they differ from this handbook. Do not approve or distribute this template until qualified counsel has reviewed it for each place where {{company_name}} employs people and the company has named its people contact, reporting routes, and required regional supplements.
|
|
8
|
+
|
|
9
|
+
## Scope and responsibility
|
|
10
|
+
|
|
11
|
+
This handbook applies to employees. Contractors follow the conduct and security requirements assigned to them under their agreements and applicable policies.
|
|
12
|
+
|
|
13
|
+
Managers are responsible for applying this handbook fairly, seeking advice when local requirements are unclear, and raising concerns instead of resolving serious matters informally. Employees are responsible for reading the handbook, asking questions, following applicable requirements, and reporting suspected violations.
|
|
14
|
+
|
|
15
|
+
Questions about employment, conduct, accommodations, pay, leave, or workplace safety should be sent to a manager or the designated people contact through the published company reporting route. Security events should be sent to {{security_contact_email}}.
|
|
16
|
+
|
|
17
|
+
## Communication and problem solving
|
|
18
|
+
|
|
19
|
+
Employees should raise routine work questions with their manager. When the issue is not resolved, cannot reasonably be raised with that manager, or affects more than one team, the employee may contact the designated people contact. Employees may also use any reporting route required by law or another company policy.
|
|
20
|
+
|
|
21
|
+
Managers should listen, gather the relevant facts, explain decisions they are authorized to make, and route matters that require another owner. Employees do not need to follow this informal path before reporting misconduct or exercising a legal right.
|
|
22
|
+
|
|
23
|
+
## Reporting concerns
|
|
24
|
+
|
|
25
|
+
Employees should promptly report suspected harassment, discrimination, retaliation, fraud, bribery, unsafe conditions, security events, misuse of data, or other policy violations. A non-security report may be made to a manager, the designated people contact, or another published independent route. Security and data events may also be reported to {{security_contact_email}}. If a person receiving reports is involved in the concern, the employee should use another route. A written report is not required.
|
|
26
|
+
|
|
27
|
+
{{company_name}} will review reports promptly and impartially, preserve relevant records, limit disclosure to people who need the information, and take appropriate corrective action when warranted. Employees must cooperate honestly. No one may retaliate against a person who makes a good-faith report, requests an accommodation, raises a pay or safety concern, or participates in a review.
|
|
28
|
+
|
|
29
|
+
## Equal opportunity and accommodations
|
|
30
|
+
|
|
31
|
+
Employment decisions are based on job-related qualifications, performance, business needs, and lawful requirements. {{company_name}} prohibits unlawful discrimination based on a characteristic protected in the employee's work location.
|
|
32
|
+
|
|
33
|
+
{{company_name}} provides reasonable accommodations for disability, religion, pregnancy and related conditions, and other protected needs when required by law. Employees may request an accommodation from their manager or the designated people contact without using special words. {{company_name}} and the employee will discuss the work limitation, possible accommodations, and any information lawfully needed to evaluate the request. Retaliation for requesting or using an accommodation is prohibited.
|
|
34
|
+
|
|
35
|
+
## Harassment and respectful conduct
|
|
36
|
+
|
|
37
|
+
Harassment, bullying, threats, and other abusive conduct are prohibited. Unlawful harassment includes unwelcome conduct tied to a protected characteristic when the conduct creates a hostile work setting or affects an employment decision.
|
|
38
|
+
|
|
39
|
+
Prohibited conduct may include slurs, insults, threats, unwanted sexual attention, repeated offensive jokes, degrading images, unwelcome touching, or conditioning a work benefit on personal or sexual conduct. Harassment can occur between people of any role or identity, and a person may report conduct even when it was directed at someone else.
|
|
40
|
+
|
|
41
|
+
These rules apply in offices, remote work, digital channels, travel, customer interactions, social events connected to work, and any other setting where conduct affects the workplace.
|
|
42
|
+
|
|
43
|
+
## Ethical conduct and conflicts
|
|
44
|
+
|
|
45
|
+
Act honestly and in the best interests of {{company_name}} while performing company work. Follow applicable laws, contracts, and company policies.
|
|
46
|
+
|
|
47
|
+
Disclose an actual or potential conflict of interest to the policy owner before taking part in the related decision. This includes a financial interest, outside role, close personal relationship, gift, or other circumstance that could affect judgment.
|
|
48
|
+
|
|
49
|
+
Do not offer, request, authorize, or accept a bribe, kickback, or improper payment. Gifts and entertainment must follow the Anti-Bribery and Corruption Policy.
|
|
50
|
+
|
|
51
|
+
Keep complete and accurate business records. Do not hide, falsify, backdate, or destroy information to mislead another person or avoid a review.
|
|
52
|
+
|
|
53
|
+
Only an authorized spokesperson may make public statements or respond to press, investor, or government inquiries on behalf of {{company_name}}.
|
|
54
|
+
|
|
55
|
+
## Confidentiality and intellectual property
|
|
56
|
+
|
|
57
|
+
Protect nonpublic information received from {{company_name}}, customers, workers, vendors, and partners. Use it only for approved work, share it only with authorized people, and follow the Data Protection and Handling Policy.
|
|
58
|
+
|
|
59
|
+
Employment terms and applicable law determine ownership of work product and intellectual property. Employees must sign any required confidentiality and invention-assignment agreements.
|
|
60
|
+
|
|
61
|
+
Confidentiality duties continue after employment ends. Nothing in this handbook prohibits lawful reporting to a regulator, discussion of working conditions, or another activity protected by law.
|
|
62
|
+
|
|
63
|
+
## Company systems and acceptable use
|
|
64
|
+
|
|
65
|
+
Use company systems, accounts, funds, devices, and other property for authorized purposes. Limited personal use may be allowed when it does not interfere with work, create material cost or risk, violate policy, or break the law.
|
|
66
|
+
|
|
67
|
+
Do not use company systems to:
|
|
68
|
+
|
|
69
|
+
- Break the law or another person's rights.
|
|
70
|
+
- Create or distribute discriminatory, harassing, threatening, obscene, or malicious material.
|
|
71
|
+
- Access systems or data without authorization.
|
|
72
|
+
- Run a personal business or political campaign without approval.
|
|
73
|
+
- Send mass unsolicited messages.
|
|
74
|
+
- Install unapproved software that creates material risk.
|
|
75
|
+
- Disable, evade, or interfere with security, monitoring, access, or retention controls.
|
|
76
|
+
|
|
77
|
+
{{company_name}} may log, review, preserve, or disclose activity on company-managed systems as allowed by law and for security, operations, support, compliance, and investigation. Employees should not expect personal privacy in company accounts or devices beyond what law and written policy require.
|
|
78
|
+
|
|
79
|
+
Employees must protect system integrity, use approved storage and communications tools, and return or delete company data and property when instructed.
|
|
80
|
+
|
|
81
|
+
## Security responsibilities
|
|
82
|
+
|
|
83
|
+
Every employee must:
|
|
84
|
+
|
|
85
|
+
- Complete assigned security and policy training within 30 days of starting and at least annually.
|
|
86
|
+
- Use a unique company identity and approved authentication methods.
|
|
87
|
+
- Enable multi-factor authentication when required.
|
|
88
|
+
- Store passwords and secrets only in approved tools.
|
|
89
|
+
- Keep devices supported, encrypted, locked when unattended, and updated.
|
|
90
|
+
- Follow data classification, clear-screen, mobile-computing, and acceptable-use requirements.
|
|
91
|
+
- Use approved systems for company work.
|
|
92
|
+
- Report suspected phishing, data loss, account compromise, policy violations, and other security events immediately to {{security_contact_email}}.
|
|
93
|
+
- Cooperate with access reviews, investigations, recovery exercises, and audit requests.
|
|
94
|
+
|
|
95
|
+
Do not bypass security controls, share accounts, or access data without a business need.
|
|
96
|
+
|
|
97
|
+
## Remote work and travel
|
|
98
|
+
|
|
99
|
+
Remote and traveling employees must maintain a work setting that protects company conversations, screens, paper records, and devices. Use trusted networks or approved secure access methods. Do not leave devices unattended in public or checked baggage.
|
|
100
|
+
|
|
101
|
+
Employees remain responsible for attendance, communication, security, safety, and work expectations regardless of location. Approval to work remotely does not authorize work from every location because tax, employment, security, and customer duties may apply.
|
|
102
|
+
|
|
103
|
+
## Employment classification and records
|
|
104
|
+
|
|
105
|
+
Written employment terms identify whether a role is full-time, part-time, temporary, exempt, non-exempt, or another classification recognized in the employee's location. Classification affects pay, timekeeping, benefits, and leave, so employees should raise questions promptly.
|
|
106
|
+
|
|
107
|
+
Employees must keep contact, tax, payment, emergency, and work-authorization records current through the approved process. {{company_name}} limits access to personnel records and uses them only for lawful business purposes.
|
|
108
|
+
|
|
109
|
+
Requests for employment verification or references must be sent to the authorized people contact.
|
|
110
|
+
|
|
111
|
+
## Work time, attendance, and pay
|
|
112
|
+
|
|
113
|
+
Employees must follow their assigned schedule, attend required meetings, and notify their manager promptly when they will be late or absent. Repeated absence, lateness, or failure to report an absence may lead to corrective action, subject to protected leave and local law.
|
|
114
|
+
|
|
115
|
+
Non-exempt employees must record all time worked accurately, including approved remote work and work outside the usual schedule. Managers must not ask an employee to work off the clock, omit time, or create a false record.
|
|
116
|
+
|
|
117
|
+
Where overtime approval applies, employees must obtain approval before working overtime. {{company_name}} will still record and pay all hours that law requires, even when the employee did not obtain advance approval. A failure to follow the approval process may be addressed separately.
|
|
118
|
+
|
|
119
|
+
Written employment terms state the pay schedule and available payment methods. Employees should review pay records and promptly report a suspected error.
|
|
120
|
+
|
|
121
|
+
## Leave, holidays, and benefits
|
|
122
|
+
|
|
123
|
+
Benefit plans, written leave policies, and regional supplements define eligibility, enrollment, coverage, holidays, paid time off, sick leave, and other benefits. The applicable plan document controls if a summary conflicts with it.
|
|
124
|
+
|
|
125
|
+
Employees should request planned leave in advance and give prompt notice when illness or an emergency makes advance notice impractical. {{company_name}} may request only the documentation allowed and needed to administer the leave.
|
|
126
|
+
|
|
127
|
+
{{company_name}} provides legally required leave and workplace support, which may include family or medical leave, disability leave, pregnancy-related leave, military leave, jury or witness duty, voting leave, work-injury leave, lactation accommodations, and other location-specific rights. A regional supplement or written policy defines duration, pay, eligibility, notice, and return-to-work rules.
|
|
128
|
+
|
|
129
|
+
{{company_name}} maintains workers' compensation insurance or equivalent coverage where required. Employees must promptly report a work-related injury or illness so the company can address safety and required benefits.
|
|
130
|
+
|
|
131
|
+
## Expenses
|
|
132
|
+
|
|
133
|
+
{{company_name}} reimburses approved business expenses under its written expense process and applicable law. Employees must obtain required approval, submit accurate records on time, and return refunds or credits. Do not split, disguise, or misclassify an expense to avoid review.
|
|
134
|
+
|
|
135
|
+
## Health, safety, and workplace security
|
|
136
|
+
|
|
137
|
+
Follow workplace safety instructions and report hazards, injuries, threats, or violence as soon as practical after becoming aware of them. Call local emergency services when someone faces an immediate threat.
|
|
138
|
+
|
|
139
|
+
Threats, intimidation, fighting, stalking, and workplace violence are prohibited. Weapons are prohibited where company rules and applicable law allow such a restriction. Employees must not work while impaired by alcohol, illegal drugs, or another substance that makes the work unsafe.
|
|
140
|
+
|
|
141
|
+
Smoking and vaping are allowed only in approved areas and as permitted by local rules. Employees must follow emergency, visitor, facility-access, and incident-reporting procedures.
|
|
142
|
+
|
|
143
|
+
## Performance and corrective action
|
|
144
|
+
|
|
145
|
+
Employees are expected to meet job requirements, follow reasonable instructions, protect company resources, and comply with policy. Managers conduct a documented performance review at least annually.
|
|
146
|
+
|
|
147
|
+
{{company_name}} may use coaching, access restrictions, warnings, reassignment, leave, or separation to address performance or conduct, subject to law and written agreements. It may choose the response suited to the facts and is not required to use a fixed sequence.
|
|
148
|
+
|
|
149
|
+
Nothing in this handbook limits lawful employee rights.
|
|
150
|
+
|
|
151
|
+
## Changes and separation
|
|
152
|
+
|
|
153
|
+
{{company_name}} may revise this handbook as its work, systems, or legal duties change. The policy owner reviews it at least annually. Git history records approvals and changes.
|
|
154
|
+
|
|
155
|
+
An employee who resigns should give at least two weeks' notice where practical. {{company_name}} may conduct an exit interview. When employment ends, the employee must return company property, records, devices, credentials, and access methods and must not keep company data.
|
|
156
|
+
|
|
157
|
+
Access is removed under the Information Security Policy. Continuing duties under confidentiality, intellectual-property, and other written agreements remain in effect.
|
|
158
|
+
|
|
159
|
+
## Acknowledgement
|
|
160
|
+
|
|
161
|
+
Employees must acknowledge the handbook and assigned policies when they join and when a material update requires a new acknowledgement. An acknowledgement confirms receipt and understanding. It does not create a contract or change lawful employment rights or written employment terms.
|
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": 1,
|
|
3
|
+
"id": "policy-information-security",
|
|
4
|
+
"type": "policy",
|
|
5
|
+
"title": "Information Security Policy",
|
|
6
|
+
"status": "draft",
|
|
7
|
+
"ownerIds": ["person-policy-owner"],
|
|
8
|
+
"approverIds": ["person-independent-approver"],
|
|
9
|
+
"policyKind": "information-security",
|
|
10
|
+
"version": "1.0",
|
|
11
|
+
"effectiveOn": "{{effective_date}}",
|
|
12
|
+
"reviewCadence": {
|
|
13
|
+
"mode": "calendar",
|
|
14
|
+
"unit": "year",
|
|
15
|
+
"interval": 1,
|
|
16
|
+
"anchorDate": "{{effective_date}}"
|
|
17
|
+
},
|
|
18
|
+
"audience": ["employees", "contractors", "vendors"],
|
|
19
|
+
"acknowledgementRequired": true,
|
|
20
|
+
"relatedPolicyIds": [
|
|
21
|
+
"policy-clear-desk-screen",
|
|
22
|
+
"policy-data-protection-handling",
|
|
23
|
+
"policy-mobile-computing-communications"
|
|
24
|
+
],
|
|
25
|
+
"controlIds": [
|
|
26
|
+
"control-security-governance",
|
|
27
|
+
"control-policy-management",
|
|
28
|
+
"control-security-communication",
|
|
29
|
+
"control-workforce-expectations",
|
|
30
|
+
"control-security-training",
|
|
31
|
+
"control-performance-review",
|
|
32
|
+
"control-risk-assessment",
|
|
33
|
+
"control-monitoring-remediation",
|
|
34
|
+
"control-access-authorization",
|
|
35
|
+
"control-strong-authentication",
|
|
36
|
+
"control-access-review-offboarding",
|
|
37
|
+
"control-physical-workspace-security",
|
|
38
|
+
"control-data-classification-inventory",
|
|
39
|
+
"control-encryption-transmission",
|
|
40
|
+
"control-data-retention-disposal",
|
|
41
|
+
"control-inventory-configuration",
|
|
42
|
+
"control-endpoint-protection",
|
|
43
|
+
"control-network-security",
|
|
44
|
+
"control-change-management",
|
|
45
|
+
"control-vulnerability-management",
|
|
46
|
+
"control-penetration-testing",
|
|
47
|
+
"control-logging-monitoring",
|
|
48
|
+
"control-incident-response",
|
|
49
|
+
"control-incident-exercise",
|
|
50
|
+
"control-backup-restoration",
|
|
51
|
+
"control-continuity-exercise",
|
|
52
|
+
"control-vendor-due-diligence",
|
|
53
|
+
"control-vendor-monitoring",
|
|
54
|
+
"control-security-exceptions"
|
|
55
|
+
],
|
|
56
|
+
"relatedDocumentIds": [
|
|
57
|
+
"document-business-continuity-disaster-recovery",
|
|
58
|
+
"document-incident-response-plan",
|
|
59
|
+
"document-data-retention-schedule"
|
|
60
|
+
]
|
|
61
|
+
}
|