CAIQLite Self Assessment
This page hosts the Consensus Assessments Initiative Questionnaire Lite (CAIQLite) v4.1.0 content used for Atlassian CCM Lite self-assessment. Source workbook: CAIQLitev4.1.0 (generated 2026-01-13).
Scope: Responses describe Be On Time practices for MSP Planner for Jira as a Marketplace app hosted on Atlassian Forge / Jira Cloud, including inherited controls from the platform where noted. This is a good-faith self-assessment, not a third-party audit report. For authoritative platform statements, see Atlassian Trust documentation.
For each control question: CCM domain, CCM control title, question ID, question, answer, implementation description.
Related: Information Security Policy.
1. A&A-02.1
CCM domain: Audit & Assurance
CCM control title: Independent Assessments
Question ID: A&A-02.1
Question:
Are independent audit and assurance assessments conducted according to relevant standards at least annually?
Answer:
Yes
Implementation description:
MSP Planner for Jira is distributed through the Atlassian Marketplace and runs on Atlassian Forge / Jira Cloud. Atlassian operates a broad assurance program for its platform and app ecosystem, including design- and build-time controls (for example pipeline checks and static analysis expectations for Marketplace apps), hosting-time security scanning and vulnerability management for deployed apps, and independent third-party audits of Atlassian services (see Atlassian’s Trust / security documentation). Be On Time monitors findings that apply to our application (for example from automated dependency and code scanning, security advisories, and Marketplace or partner security requirements), records them with owners and due dates, and implements corrective action plans with tracked remediation until closure and verification. Independent assurance on the underlying platform is performed by Atlassian’s third-party audit program on a recurring basis; we align our app security work with those expectations and with our own release testing.
2. A&A-03.1
CCM domain: Audit & Assurance
CCM control title: Risk Based Planning Assessment
Question ID: A&A-03.1
Question:
Are independent audit and assurance assessments performed according to risk-based plans and policies, and in response to significant changes or emerging risks?
Answer:
Yes
Implementation description:
MSP Planner for Jira is distributed through the Atlassian Marketplace and runs on Atlassian Forge / Jira Cloud. Atlassian operates a broad assurance program for its platform and app ecosystem, including design- and build-time controls (for example pipeline checks and static analysis expectations for Marketplace apps), hosting-time security scanning and vulnerability management for deployed apps, and independent third-party audits of Atlassian services (see Atlassian’s Trust / security documentation). Be On Time monitors findings that apply to our application (for example from automated dependency and code scanning, security advisories, and Marketplace or partner security requirements), records them with owners and due dates, and implements corrective action plans with tracked remediation until closure and verification. We prioritize remediation by risk (severity, exploitability, customer and data impact, and regulatory context) and re-plan when there are significant product or infrastructure changes.
3. A&A-04.1
CCM domain: Audit & Assurance
CCM control title: Requirements Compliance
Question ID: A&A-04.1
Question:
Is compliance verified regarding all relevant standards, regulations, legal/contractual, and statutory requirements applicable to the audit?
Answer:
Yes
Implementation description:
Our scope includes applicable data protection law (including GDPR where relevant), the Atlassian Marketplace Partner Agreement and product terms, and customer contractual commitments. We map control expectations to our Information Security Policy (published on this site) and to operational procedures, and we review coverage when regulations or Marketplace requirements change.
4. A&A-06.1
CCM domain: Audit & Assurance
CCM control title: Remediation
Question ID: A&A-06.1
Question:
Is a risk-based corrective action plan to remediate audit findings established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
We maintain a documented corrective-action process for security and compliance findings: intake/triage, owner assignment, remediation plan, implementation, verification (including re-test or scan where appropriate), and closure evidence. This applies to findings from automated scanning, dependency alerts, internal review, and Atlassian / Marketplace-related security expectations affecting our app.
5. A&A-06.2
CCM domain: Audit & Assurance
CCM control title: Remediation
Question ID: A&A-06.2
Question:
Is the remediation status of audit findings regularly reviewed and reported to relevant stakeholders?
Answer:
Yes
Implementation description:
Open remediation items are reviewed on a recurring cadence (at least monthly internally). Material items are escalated and status is communicated to stakeholders responsible for product delivery until closed.
6. AIS-02.1
CCM domain: Application & Interface Security
CCM control title: Application Security Baseline Requirements
Question ID: AIS-02.1
Question:
Are baseline requirements to secure applications established, documented, and maintained?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
7. AIS-04.1
CCM domain: Application & Interface Security
CCM control title: Secure Application Development Lifecycle
Question ID: AIS-04.1
Question:
Is a secure SDLC process defined and implemented for application requirements analysis, planning, design, development, testing, deployment, and operation per organizationally designed security requirements?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
8. AIS-06.1
CCM domain: Application & Interface Security
CCM control title: Secure Application Deployment
Question ID: AIS-06.1
Question:
Are strategies and capabilities established and implemented to deploy application code in a secure, standardized, and compliant manner?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
9. AIS-06.2
CCM domain: Application & Interface Security
CCM control title: Secure Application Deployment
Question ID: AIS-06.2
Question:
Is the deployment and integration of application code automated where possible?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
10. AIS-07.1
CCM domain: Application & Interface Security
CCM control title: Application Vulnerability Remediation
Question ID: AIS-07.1
Question:
Are application security vulnerabilities remediated following defined processes?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
11. AIS-07.2
CCM domain: Application & Interface Security
CCM control title: Application Vulnerability Remediation
Question ID: AIS-07.2
Question:
Is the remediation of application security vulnerabilities automated when possible?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
12. AIS-08.1
CCM domain: Application & Interface Security
CCM control title: API Security
Question ID: AIS-08.1
Question:
Are processes, procedures, and technical measures defined and implemented to secure APIs?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
13. AIS-08.2
CCM domain: Application & Interface Security
CCM control title: API Security
Question ID: AIS-08.2
Question:
Are reviews and updates for any improvements conducted at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
We maintain documented baseline requirements for our TypeScript/React codebase: typed APIs, linting, peer code review, automated tests in CI, dependency updates, and secure handling of secrets and tokens. Apps are built and deployed through Atlassian Forge / Marketplace pipelines with repeatable builds.
14. BCR-01.1
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Business Continuity Management Policy and Procedures
Question ID: BCR-01.1
Question:
Are business continuity management and operational resilience policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
15. BCR-01.2
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Business Continuity Management Policy and Procedures
Question ID: BCR-01.2
Question:
Are the policies and procedures reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
16. BCR-02.1
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Risk Assessment and Impact Analysis
Question ID: BCR-02.1
Question:
Are criteria for developing business continuity and operational resiliency strategies and capabilities established based on business disruption and risk impacts?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
17. BCR-02.2
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Risk Assessment and Impact Analysis
Question ID: BCR-02.2
Question:
Are the risk assessment and impact analysis reviewed and updated at least annually or upon significant changes?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
18. BCR-03.1
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Business Continuity Strategy
Question ID: BCR-03.1
Question:
Are strategies being established to reduce the impact of business disruptions, and are resiliency and recovery from business disruptions being improved?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
19. BCR-08.1
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Backup
Question ID: BCR-08.1
Question:
Are backups performed periodically?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
20. BCR-08.2
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Backup
Question ID: BCR-08.2
Question:
Is the confidentiality, integrity, and availability of the backup ensured?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
21. BCR-08.3
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Backup
Question ID: BCR-08.3
Question:
Can backups be restored appropriately for resiliency?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
22. BCR-09.1
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Disaster Response Plan
Question ID: BCR-09.1
Question:
Is a disaster response plan established, documented, approved, applied, evaluated, and maintained to ensure recovery from natural and man-made disasters?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
23. BCR-09.2
CCM domain: Business Continuity Management and Operational Resilience
CCM control title: Disaster Response Plan
Question ID: BCR-09.2
Question:
Is the disaster response plan updated at least annually, and when significant changes occur?
Answer:
Yes
Implementation description:
Service continuity for the hosted product relies on Atlassian Forge / Jira Cloud availability and published SLAs. We maintain internal continuity basics: on-call ownership for incidents, documented recovery steps for our components, backups of source code and configuration in Git, and communication paths to customers via support channels.
24. CCC-01.1
CCM domain: Change Control and Configuration Management
CCM control title: Change Management Policy and Procedures
Question ID: CCC-01.1
Question:
Are policies and procedures for managing the risks associated with applying changes to assets owned, controlled, or used by the organization established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
25. CCC-01.2
CCM domain: Change Control and Configuration Management
CCM control title: Change Management Policy and Procedures
Question ID: CCC-01.2
Question:
Are the policies and procedures reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
26. CCC-02.1
CCM domain: Change Control and Configuration Management
CCM control title: Quality Testing
Question ID: CCC-02.1
Question:
Is a defined quality change control, approval and testing process, incorporating baselines, testing, and release standards, established, maintained and implemented?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
27. CCC-04.1
CCM domain: Change Control and Configuration Management
CCM control title: Unauthorized Change Protection
Question ID: CCC-04.1
Question:
Is a procedure to authorize the addition, removal, update, and management of assets owned, controlled, or used by the organization, implemented and enforced?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
28. CCC-05.1
CCM domain: Change Control and Configuration Management
CCM control title: Change Agreements
Question ID: CCC-05.1
Question:
Are provisions to limit changes directly impacting service customer-owned environments (tenants) to explicitly authorized requests included within service level agreements?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
29. CCC-06.1
CCM domain: Change Control and Configuration Management
CCM control title: Change Management Baseline
Question ID: CCC-06.1
Question:
Are change management and configuration baselines established, documented and implemented for all relevant authorized changes on organizational assets?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
30. CCC-06.2
CCM domain: Change Control and Configuration Management
CCM control title: Change Management Baseline
Question ID: CCC-06.2
Question:
Are the baselines reviewed and updated at least annually or upon significant changes?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
31. CCC-07.1
CCM domain: Change Control and Configuration Management
CCM control title: Detection of Baseline Deviation
Question ID: CCC-07.1
Question:
Are detection measures implemented with proactive notification if changes deviate from established baselines?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
32. CCC-09.1
CCM domain: Change Control and Configuration Management
CCM control title: Change Restoration
Question ID: CCC-09.1
Question:
Is a process to proactively roll back changes to a previously known "good state" defined and implemented in case of errors or security concerns?
Answer:
Yes
Implementation description:
Changes flow through version control with pull requests, review, and automated checks where configured. Production releases follow a defined release process. Unauthorized changes to our repositories and build accounts are mitigated via MFA, least-privilege access, and provider-side controls (Forge/Git hosting).
33. CEK-01.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Encryption and Key Management Policy and Procedures
Question ID: CEK-01.1
Question:
Are cryptography, encryption, and key management policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
34. CEK-01.2
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Encryption and Key Management Policy and Procedures
Question ID: CEK-01.2
Question:
Are cryptography, encryption, and key management policies and procedures reviewed and updated at least annually, upon significant changes?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
35. CEK-02.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: CEK Roles and Responsibilities
Question ID: CEK-02.1
Question:
Are cryptography, encryption, and key management roles and responsibilities defined and implemented?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
36. CEK-03.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Data Protection
Question ID: CEK-03.1
Question:
Are data protection at-rest and in-transit, and where applicable in use, provided using cryptographic libraries certified to approved standards?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
37. CEK-04.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Encryption Algorithm
Question ID: CEK-04.1
Question:
Are encryption algorithms following industry standards utilized for protecting data, based on the data classification and associated risks?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
38. CEK-05.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Encryption Change Management
Question ID: CEK-05.1
Question:
Are standard change management procedures established to review, approve, implement and communicate cryptography, encryption, and key management technology changes that accommodate internal and external sources?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
39. CEK-10.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Key Generation
Question ID: CEK-10.1
Question:
Are cryptographic keys generated using industry-accepted and approved cryptographic libraries that specify algorithm strength and random number generator specifications?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
40. CEK-12.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Key Rotation
Question ID: CEK-12.1
Question:
Are cryptographic keys rotated based on a cryptoperiod calculated while considering information disclosure risks and legal and regulatory requirements?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
41. CEK-13.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Key Revocation
Question ID: CEK-13.1
Question:
Are cryptographic keys revoked and removed before the end of the established cryptoperiod (when a key is compromised, or an entity is no longer part of the organization) per defined, implemented, and evaluated processes, procedures, and technical measures to include legal and regulatory requirement provisions?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
42. CEK-14.1
CCM domain: Cryptography, Encryption & Key Management
CCM control title: Key Destruction
Question ID: CEK-14.1
Question:
Are processes, procedures and technical measures to securely destroy cryptographic keys when they are no longer needed, defined, implemented, and evaluated, and include provisions for legal and regulatory requirements?
Answer:
Yes
Implementation description:
Cryptographic controls for data in transit and at rest in the Forge/Jira Cloud runtime are provided by Atlassian and underlying cloud infrastructure per Atlassian documentation. We follow Forge secret storage practices for app credentials and avoid embedding secrets in source code.
43. DCS-04.1
CCM domain: Datacenter Security
CCM control title: Secure Area Policy and Procedures
Question ID: DCS-04.1
Question:
Are policies and procedures for maintaining a safe and secure working environment (in offices, rooms, and facilities) established, documented, approved, communicated, enforced, and maintained?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
44. DCS-04.2
CCM domain: Datacenter Security
CCM control title: Secure Area Policy and Procedures
Question ID: DCS-04.2
Question:
Are policies and procedures for maintaining safe, secure working environments (e.g., offices, rooms) reviewed and updated at least annually, or upon significant changes?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
45. DCS-06.1
CCM domain: Datacenter Security
CCM control title: Assets Classification
Question ID: DCS-06.1
Question:
Is the classification and documentation of physical and logical assets based on the organizational business risk?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
46. DCS-06.2
CCM domain: Datacenter Security
CCM control title: Assets Classification
Question ID: DCS-06.2
Question:
Are assets’ classifications reviewed and updated at least annually or upon significant changes?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
47. DCS-07.1
CCM domain: Datacenter Security
CCM control title: Assets Cataloguing and Tracking
Question ID: DCS-07.1
Question:
Are all relevant physical and logical assets at all CSP sites cataloged and tracked within a secured system?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
48. DCS-07.2
CCM domain: Datacenter Security
CCM control title: Assets Cataloguing and Tracking
Question ID: DCS-07.2
Question:
Is the catalogue reviewed and updated at least annually or upon significant changes?
Answer:
Not applicable (inherited)
Implementation description:
We do not operate our own data centers. Production workloads for the Marketplace app run on Atlassian-managed infrastructure; physical and environmental controls are covered by Atlassian’s assurance program and public compliance materials.
49. DSP-01.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Security and Privacy Policy and Procedures
Question ID: DSP-01.1
Question:
Are policies and procedures established, documented, approved, communicated, enforced, evaluated, and maintained for the preparation, classification, protection, and handling of data throughout its lifecycle according to all applicable laws and regulations, standards, and risk level?
Answer:
Yes
Implementation description:
We maintain a lightweight data inventory for the app: categories of data processed (largely Jira issue and project metadata needed for planning), purposes, and flows between the customer tenant and Forge. Details are aligned with our Privacy Policy and security documentation.
50. DSP-01.2
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Security and Privacy Policy and Procedures
Question ID: DSP-01.2
Question:
Are data security and privacy policies and procedures reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
51. DSP-03.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Inventory
Question ID: DSP-03.1
Question:
Is a data inventory created and maintained for sensitive, regulated and personal information (at a minimum)?
Answer:
Yes
Implementation description:
We maintain a lightweight data inventory for the app: categories of data processed (largely Jira issue and project metadata needed for planning), purposes, and flows between the customer tenant and Forge. Details are aligned with our Privacy Policy and security documentation.
52. DSP-03.2
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Inventory
Question ID: DSP-03.2
Question:
Is the inventory reviewed and updated at least annually or upon significant changes?
Answer:
Yes
Implementation description:
We maintain a lightweight data inventory for the app: categories of data processed (largely Jira issue and project metadata needed for planning), purposes, and flows between the customer tenant and Forge. Details are aligned with our Privacy Policy and security documentation.
53. DSP-04.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Classification
Question ID: DSP-04.1
Question:
Is data classified according to type and sensitivity levels?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
54. DSP-05.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Flow Documentation
Question ID: DSP-05.1
Question:
Is data flow documentation created to identify what data is processed and where it is stored and transmitted?
Answer:
Yes
Implementation description:
We maintain a lightweight data inventory for the app: categories of data processed (largely Jira issue and project metadata needed for planning), purposes, and flows between the customer tenant and Forge. Details are aligned with our Privacy Policy and security documentation.
55. DSP-05.2
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Flow Documentation
Question ID: DSP-05.2
Question:
Is data flow documentation reviewed at defined intervals, at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
We maintain a lightweight data inventory for the app: categories of data processed (largely Jira issue and project metadata needed for planning), purposes, and flows between the customer tenant and Forge. Details are aligned with our Privacy Policy and security documentation.
56. DSP-06.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Ownership and Stewardship
Question ID: DSP-06.1
Question:
Is the ownership and stewardship of all relevant personal and sensitive data documented?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
57. DSP-06.2
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Ownership and Stewardship
Question ID: DSP-06.2
Question:
Is data ownership and stewardship documentation reviewed at least annually?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
58. DSP-07.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Protection by Design and Default
Question ID: DSP-07.1
Question:
Are systems, products, and business practices based on security principles by design and per industry best practices?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
59. DSP-08.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Privacy by Design and Default
Question ID: DSP-08.1
Question:
Are systems, products, and business practices based on privacy principles by design and according to industry best practices?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
60. DSP-08.2
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Privacy by Design and Default
Question ID: DSP-08.2
Question:
Are systems' privacy settings configured by default and according to all applicable laws and regulations?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
61. DSP-10.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Sensitive Data Transfer
Question ID: DSP-10.1
Question:
Are processes, procedures, and technical measures defined, implemented, and evaluated to ensure any transfer of personal or sensitive data is protected from unauthorized access and only processed within scope (as permitted by respective laws and regulations)?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
62. DSP-11.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Personal Data Access, Reversal, Rectification and Deletion
Question ID: DSP-11.1
Question:
Are processes, procedures, and technical measures defined, implemented, and evaluated to enable data subjects to request access to, modify, or delete personal data (per applicable laws and regulations)?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
63. DSP-12.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Limitation of Purpose in Personal Data Processing
Question ID: DSP-12.1
Question:
Are processes, procedures, and technical measures defined, implemented, and evaluated to ensure personal data is processed (per applicable laws and regulations and for the purposes declared to the data subject)?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
64. DSP-13.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Personal Data Sub-processing
Question ID: DSP-13.1
Question:
Are processes, procedures, and technical measures defined, implemented, and evaluated for the transfer and sub-processing of personal data within the service supply chain (according to any applicable laws and regulations)?
Answer:
Yes
Implementation description:
Primary sub-processor for product operation is Atlassian (Forge / Jira Cloud). Additional processors (for example email or analytics used only on the marketing site) are listed or referenced in our Privacy Policy where applicable. We review agreements for security and data-processing terms.
65. DSP-14.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Disclosure of Data Sub-processors
Question ID: DSP-14.1
Question:
Are processes, procedures, and technical measures defined, implemented, and evaluated to disclose details to the data owner of any personal or sensitive data access by sub-processors before processing initiation?
Answer:
Yes
Implementation description:
Primary sub-processor for product operation is Atlassian (Forge / Jira Cloud). Additional processors (for example email or analytics used only on the marketing site) are listed or referenced in our Privacy Policy where applicable. We review agreements for security and data-processing terms.
66. DSP-16.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Retention and Deletion
Question ID: DSP-16.1
Question:
Do data retention, archiving, and deletion practices follow business requirements, applicable laws, and regulations?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
67. DSP-17.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Sensitive Data Protection
Question ID: DSP-17.1
Question:
Are processes, procedures, and technical measures defined and implemented to protect sensitive data throughout its lifecycle?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
68. DSP-19.1
CCM domain: Data Security and Privacy Lifecycle Management
CCM control title: Data Location
Question ID: DSP-19.1
Question:
Are processes, procedures, and technical measures defined and implemented to specify and document physical data locations, including locales where data is processed or backed up?
Answer:
Yes
Implementation description:
Security and privacy expectations are documented in our Information Security Policy and Privacy Policy. We apply data minimization for app features, review changes for privacy impact where relevant, and support customer rights requests as described in the Privacy Policy.
69. GRC-01.1
CCM domain: Governance, Risk and Compliance
CCM control title: Governance Program Policy and Procedures
Question ID: GRC-01.1
Question:
Are information governance program policies and procedures sponsored by organizational leadership established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
70. GRC-01.2
CCM domain: Governance, Risk and Compliance
CCM control title: Governance Program Policy and Procedures
Question ID: GRC-01.2
Question:
Are the policies and procedures reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
71. GRC-02.1
CCM domain: Governance, Risk and Compliance
CCM control title: Risk Management Program
Question ID: GRC-02.1
Question:
Is there an established and maintained formal, documented, and leadership-sponsored enterprise risk management (ERM) program that includes policies and procedures for identification, evaluation, ownership, treatment, and acceptance of risks?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
72. GRC-06.1
CCM domain: Governance, Risk and Compliance
CCM control title: Governance Responsibility Model
Question ID: GRC-06.1
Question:
Are roles and responsibilities for planning, implementing, operating, assessing, and improving governance programs defined and documented?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
73. GRC-07.1
CCM domain: Governance, Risk and Compliance
CCM control title: Information System Regulatory Mapping
Question ID: GRC-07.1
Question:
Are all relevant standards, regulations, legal/contractual, and statutory requirements applicable to your organization identified and documented?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
74. GRC-07.2
CCM domain: Governance, Risk and Compliance
CCM control title: Information System Regulatory Mapping
Question ID: GRC-07.2
Question:
Are the identified requirements reviewed at least annually or upon significant changes?
Answer:
Yes
Implementation description:
Governance is lightweight and appropriate to company size: named ownership for security topics, annual (or more frequent) policy review, risk discussions tied to releases and vendors, and alignment with Atlassian Marketplace obligations. See our published Information Security Policy.
75. HRS-03.1
CCM domain: Human Resources
CCM control title: Clean Desk Policy and Procedures
Question ID: HRS-03.1
Question:
Are policies and procedures requiring unattended workspaces to conceal confidential data established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
We apply reasonable startup-scale HR security practices: confidentiality expectations for staff and contractors, security awareness on onboarding and when practices change, and remote-work guidance (acceptable use, device hygiene, MFA for corporate and production-related systems).
76. HRS-03.2
CCM domain: Human Resources
CCM control title: Clean Desk Policy and Procedures
Question ID: HRS-03.2
Question:
Are policies and procedures requiring unattended workspaces to conceal confidential data reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
We apply reasonable startup-scale HR security practices: confidentiality expectations for staff and contractors, security awareness on onboarding and when practices change, and remote-work guidance (acceptable use, device hygiene, MFA for corporate and production-related systems).
77. HRS-04.1
CCM domain: Human Resources
CCM control title: Remote and Home Working Policy and Procedures
Question ID: HRS-04.1
Question:
Are policies and procedures to protect information accessed, processed, or stored at remote sites and locations established, documented, approved, communicated, applied, evaluated, and maintained?
Answer:
Yes
Implementation description:
We apply reasonable startup-scale HR security practices: confidentiality expectations for staff and contractors, security awareness on onboarding and when practices change, and remote-work guidance (acceptable use, device hygiene, MFA for corporate and production-related systems).
78. HRS-04.2
CCM domain: Human Resources
CCM control title: Remote and Home Working Policy and Procedures
Question ID: HRS-04.2
Question:
Are policies and procedures to protect information accessed, processed, or stored at remote sites and locations reviewed and updated at least annually, or upon significant changes?
Answer:
Yes
Implementation description:
We apply reasonable startup-scale HR security practices: confidentiality expectations for staff and contractors, security awareness on onboarding and when practices change, and remote-work guidance (acceptable use, device hygiene, MFA for corporate and production-related systems).