rohit/probo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

First step of mitigation migration

Browse Source 
Signed-off-by: gearnode <bryan@frimin.fr>
This commit is contained in:
gearnode
2025-03-27 23:34:35 +01:00
parent 449bd620da
commit 7321862ba9
62 changed files with 4025 additions and 2141 deletions
Download Patch File Download Diff File Expand all files Collapse all files

620
data/frameworks/ISO27001-2022.json Normal file
View File

@@ -0,0 +1,620 @@
{
"name": "ISO/IEC 27001:2022",
"controls": [
{
"id": "C.4.1",
"name": "Understanding the organization and its context",
"description": "The organization shall determine external and internal issues that are relevant to its purpose and that affect its ability to achieve the intended outcome(s) of its information security management system."
},
{
"id": "C.4.2",
"name": "Understanding the needs of interested parties",
"description": "The organization shall determine: \n\na) interested parties that are relevant to the information security management system; \n\nb) the relevant requirements of these interested parties; \n\nc) which of these requirements will be addressed through the information security management system."
},
{
"id": "C.4.3",
"name": "Determining the scope of the information security management system",
"description": "The organization shall determine the boundaries and applicability of the information security management system to establish its scope. When determining this scope, the organization shall consider: \n\na) the external and internal issues referred to in 4.1; \n\nb) the requirements referred to in 4.2; \n\nc) interfaces and dependencies between activities performed by the organization, and those that are performed by other organizations. \n\nThe scope shall be available as documented information."
},
{
"id": "C.4.4",
"name": "Information security management system",
"description": "The organization shall establish, implement, maintain and continually improve an information security management system, including the processes needed and their interactions, in accordance with the requirements of ISO 27001."
},
{
"id": "C.5.1",
"name": "Leadership and commitment",
"description": "Top management shall demonstrate leadership and commitment with respect to the information security management system by: \n\na) ensuring the information security policy and the information security objectives are established and are compatible with the strategic direction of the organization; \n\nb) ensuring the integration of the information security management system requirements into the organization’s processes; \n\nc) ensuring that the resources needed for the information security management system are available; \n\nd) communicating the importance of effective information security management and of conforming to the information security management system requirements; \n\ne) ensuring that the information security management system achieves its intended outcome(s); \n\nf) directing and supporting persons to contribute to the effectiveness of the information security management system; \n\ng) promoting continual improvement; and \n\nh) supporting other relevant management roles to demonstrate their leadership as it applies to their areas of responsibility."
},
{
"id": "C.5.2",
"name": "Policy",
"description": "Top management shall establish an information security policy that: \n\na) is appropriate to the purpose of the organization; \n\nb) includes information security objectives (see 6.2) or provides the framework for setting information security objectives; \n\nc) includes a commitment to satisfy applicable requirements related to information security; \n\nd) includes a commitment to continual improvement of the information security management system.\n\nThe information security policy shall: \n\ne) be available as documented information; \n\nf) be communicated within the organization; \n\ng) be available to interested parties, as appropriate."
},
{
"id": "C.5.3",
"name": "Organizational roles, responsibilities and authorities",
"description": "Top management shall ensure that the responsibilities and authorities for roles relevant to information security are assigned and communicated within the organization. \n\nTop management shall assign the responsibility and authority for: \n\na) ensuring that the information security management system conforms to the requirements of this document; \n\nb) reporting on the performance of the information security management system to top management."
},
{
"id": "C.6.1.1",
"name": "General actions to address risks and opportunities",
"description": "When planning for the information security management system, the organization shall consider the issues referred to in 4.1 and the requirements referred to in 4.2 and determine the risks and opportunities that need to be addressed to: \n\na) ensure the information security management system can achieve its intended outcome(s); \n\nb) prevent, or reduce, undesired effects; \n\nc) achieve continual improvement.\n\nThe organization shall plan: \n\nd) actions to address these risks and opportunities; and \n\ne) how to \n 1) integrate and implement the actions into its information security management system processes; and \n 2) evaluate the effectiveness of these actions"
},
{
"id": "C.6.1.2",
"name": "Information security risk assessment",
"description": "The organization shall define and apply an information security risk assessment process that: \n\na) establishes and maintains information security risk criteria that include: \n 1) the risk acceptance criteria; and \n 2) criteria for performing information security risk assessments; \n\nb) ensures that repeated information security risk assessments produce consistent, valid and comparable results; \n\nc) identifies the information security risks: \n 1) apply the information security risk assessment process to identify risks associated with the loss of confidentiality, integrity and availability for information within the scope of the information security management system; and \n 2) identify the risk owners; \n\nd) analyses the information security risks: \n 1) assess the potential consequences that would result if the risks identified in 6.1.2 c) 1) were to materialize; \n 2) assess the realistic likelihood of the occurrence of the risks identified in 6.1.2 c) 1); and \n 3) determine the levels of risk; \n\ne) evaluates the information security risks: \n 1) compare the results of risk analysis with the risk criteria established in 6.1.2 a); and \n 2) prioritize the analysed risks for risk treatment. \n\nThe organization shall retain documented information about the information security risk assessment process."
},
{
"id": "C.6.1.3",
"name": "Information security risk treatment",
"description": "The organization shall define and apply an information security risk treatment process to: \n\na) select appropriate information security risk treatment options, taking account of the risk assessment results; \n\nb) determine all controls that are necessary to implement the information security risk treatment option(s) chosen; \n\nc) compare the controls determined in 6.1.3 b) above with those in Annex A and verify that no necessary controls have been omitted; \n\nd) produce a Statement of Applicability that contains: \n\n— the necessary controls (see 6.1.3 b) and c)); \n\n — justification for their inclusion; \n\n — whether the necessary controls are implemented or not; and \n\n — the justification for excluding any of the Annex A controls. \n\ne) formulate an information security risk treatment plan; and \n\nf) obtain risk owners’ approval of the information security risk treatment plan and acceptance of the residual information security risks. \n\nThe organization shall retain documented information about the information security risk treatment process."
},
{
"id": "C.6.2",
"name": "Information security objective and planning to achieve them",
"description": "The organization shall establish information security objectives at relevant functions and levels. The information security objectives shall:\n\na) be consistent with the information security policy; \n\nb) be measurable (if practicable); \n\nc) take into account applicable information security requirements, and results from risk assessment and risk treatment; \n\nd) be monitored; \n\ne) be communicated; \n\nf) be updated as appropriate; \n\ng) be available as documented information. \n\nThe organization shall retain documented information on the information security objectives. \n\nWhen planning how to achieve its information security objectives, the organization shall determine: \n\nh) what will be done; \n\ni) what resources will be required; \n\nj) who will be responsible; \n\nk) when it will be completed; and \n\nl) how the results will be evaluated."
},
{
"id": "C.6.3",
"name": "Planning of Changes",
"description": "When the organization determines the need for changes to the information security management system, the changes shall be carried out in a planned manner."
},
{
"id": "C.7.1",
"name": "Resources",
"description": "The organization shall determine and provide the resources needed for the establishment, implementation, maintenance and continual improvement of the information security management system."
},
{
"id": "C.7.2",
"name": "Competence",
"description": "The organization shall:\n\na) determine the necessary competence of person(s) doing work under its control that affects its information security performance; \n\nb) ensure that these persons are competent on the basis of appropriate education, training, or experience; \n\nc) where applicable, take actions to acquire the necessary competence, and evaluate the effectiveness of the actions taken; and \n\nd) retain appropriate documented information as evidence of competence."
},
{
"id": "C.7.3",
"name": "Awareness",
"description": "Persons doing work under the organization’s control shall be aware of:\n\na) the information security policy; \n\nb) their contribution to the effectiveness of the information security management system, including the benefits of improved information security performance; and \n\nc) the implications of not conforming with the information security management system requirements."
},
{
"id": "C.7.4",
"name": "Communication",
"description": "The organization shall determine the need for internal and external communications relevant to the information security management system including: \n\na) on what to communicate;\n\nb) when to communicate;\n\nc) with whom to communicate;\n\nd) how to communicate."
},
{
"id": "C.7.5.1",
"name": "Documented information",
"description": "The organization’s information security management system shall include: \n\na) documented information required by this document; and \n\nb) documented information determined by the organization as being necessary for the effectiveness of the information security management system."
},
{
"id": "C.7.5.2",
"name": "Creating and Updating",
"description": "When creating and updating documented information the organization shall ensure appropriate:\n\na) identification and description (e.g. a title, date, author, or reference number);\n\nb) format (e.g. language, software version, graphics) and media (e.g. paper, electronic); and\n\nc) review and approval for suitability and adequacy."
},
{
"id": "C.7.5.3",
"name": "Control of documented information",
"description": "Documented information required by the information security management system and by this document shall be controlled to ensure: \n\na) it is available and suitable for use, where and when it is needed; and\n\nb) it is adequately protected (e.g. from loss of confidentiality, improper use, or loss of integrity). \n\nFor the control of documented information, the organization shall address the following activities, as applicable: \n\nc) distribution, access, retrieval and use;\n\nd) storage and preservation, including the preservation of legibility;\n\ne) control of changes (e.g. version control); and\n\nf) retention and disposition. \n\nDocumented information of external origin, determined by the organization to be necessary for the planning and operation of the information security management system, shall be identified as appropriate, and controlled."
},
{
"id": "C.8.1",
"name": "Operation planning and control",
"description": "The organization shall plan, implement and control the processes needed to meet requirements, and to implement the actions determined in Clause 6, by:\n\n— establishing criteria for the processes;\n\n— implementing control of the processes in accordance with the criteria. \n\nDocumented information shall be available to the extent necessary to have confidence that the processes have been carried out as planned. \n\nThe organization shall control planned changes and review the consequences of unintended changes, taking action to mitigate any adverse effects, as necessary. \n\nThe organization shall ensure that externally provided processes, products or services that are relevant to the information security management system are controlled."
},
{
"id": "C.8.2",
"name": "Information security risk assessment",
"description": "The organization shall perform information security risk assessments at planned intervals or when significant changes are proposed or occur, taking account of the criteria established in 6.1.2 a). \n\nThe organization shall retain documented information of the results of the information security risk assessments."
},
{
"id": "C.8.3",
"name": "Information security risk treatment",
"description": "The organization shall retain documented information of the results of the information security risk treatment."
},
{
"id": "C.9.1",
"name": "Monitoring, measurement, analysis, and evaluation",
"description": "The organization shall determine:\n\na) what needs to be monitored and measured, including information security processes and controls; \n\nb) the methods for monitoring, measurement, analysis and evaluation, as applicable, to ensure valid results. The methods selected should produce comparable and reproducible results to be considered valid; \n\nc) when the monitoring and measuring shall be performed; \n\nd) who shall monitor and measure; \n\ne) when the results from monitoring and measurement shall be analyzed and evaluated; \n\nf) who shall analyze and evaluate these results. \n\nDocumented information shall be available as evidence of the results. \n\nThe organization shall evaluate the information security performance and the effectiveness of the information security management system."
},
{
"id": "C.9.2.1",
"name": "Internal Audit - General",
"description": "The organization shall conduct internal audits at planned intervals to provide information on whether the information security management system: \n\na) conforms to\n 1) the organization’s own requirements for its information security management system; \n 2) the requirements of this document;\n\nb) is effectively implemented and maintained."
},
{
"id": "C.9.2.2",
"name": "Internal Audit Program",
"description": "The organization shall plan, establish, implement and maintain an audit programme(s), including the frequency, methods, responsibilities, planning requirements and reporting. \n\nWhen establishing the internal audit programme(s), the organization shall consider the importance of the processes concerned and the results of previous audits. \n\nThe organization shall: \n\na) define the audit criteria and scope for each audit;\n \nb) select auditors and conduct audits that ensure objectivity and the impartiality of the audit process; \n\nc) ensure that the results of the audits are reported to relevant management; \n\nDocumented information shall be available as evidence of the implementation of the audit programme(s) and the audit results."
},
{
"id": "C.9.3.1",
"name": "Management review - General",
"description": "Top management shall review the organization's information security management system at planned intervals to ensure its continuing suitability, adequacy and effectiveness."
},
{
"id": "C.9.3.2",
"name": "Management review inputs",
"description": "The management review shall include consideration of: \n\na) the status of actions from previous management reviews; \n\nb) changes in external and internal issues that are relevant to the information security management system; \n\nc) changes in needs and expectations of interested parties that are relevant to the information security management system; \n\nd) feedback on the information security performance, including trends in: \n 1) nonconformities and corrective actions;\n 2) monitoring and measurement results;\n 3) audit results; \n 4) fulfilment of information security objectives;\n\ne) feedback from interested parties;\n\nf) results of risk assessment and status of risk treatment plan; \n\ng) opportunities for continual improvement."
},
{
"id": "C.9.3.3",
"name": "Management review results",
"description": "The results of the management review shall include decisions related to continual improvement opportunities and any needs for changes to the information security management system.\n\nDocumented information shall be available as evidence of the results of management reviews."
},
{
"id": "C.10.1",
"name": "Continual Improvement",
"description": "The organization shall continually improve the suitability, adequacy and effectiveness of the information security management system."
},
{
"id": "C.10.2",
"name": "Nonconformity and corrective action",
"description": "When a Nonconformity occurs, the organization shall:\n\na) React to the nonconformity, and as applicable:\n 1) take action to control and correct it;\n 2) deal with the consequences\n\nb) evaluate the need for action to eliminate the causes of nonconformity, in order that it does not recur or occur elsewhere, by;\n 1) reviewing the nonconformity;\n 2) determining the causes of the nonconformity; and\n 3) determining if similar nonconformities exist, or could potentially occur\n\nc) implement any action needed;\n\nd) review the effectiveness of any corrective action taken; and\n\ne) make changes to the information security management system, if necessary. \n\nCorrective actions shall be appropriate to the effects of the nonconformities encountered.\n\nDocumented information shall be available as evidence of:\n\nf) The nature of the nonconformities and any subsequent actions taken,\n\ng) the results of any corrective action."
},
{
"id": "A.5.1",
"name": "Policies for information security",
"description": "Information security policy and topic-specific policies shall be defined, approved by management, published, communicated to and acknowledged by relevant personnel and relevant interested parties, and reviewed at planned intervals and if significant changes occur."
},
{
"id": "A.5.2",
"name": "Information security roles and responsibilities",
"description": "Information security roles and responsibilities shall be defined and allocated according to the organization needs."
},
{
"id": "A.5.3",
"name": "Segregation of duties",
"description": "Conflicting duties and conflicting areas of responsibility shall be segregated."
},
{
"id": "A.5.4",
"name": "Management responsibilities",
"description": "Management shall require all personnel to apply information security in accordance with the established information security policy, topic-specific policies and procedures of the organization."
},
{
"id": "A.5.5",
"name": "Contact with authorities",
"description": "The organization shall establish and maintain contact with relevant authorities."
},
{
"id": "A.5.6",
"name": "Contact with special interest groups",
"description": "The organization shall establish and maintain contact with special interest groups or other specialist security forums and professional associations."
},
{
"id": "A.5.7",
"name": "Threat Intelligence",
"description": "Information relating to information security threats shall be collected and analyzed to produce threat intelligence."
},
{
"id": "A.5.8",
"name": "Information security in project management",
"description": "Information security shall be integrated into project management."
},
{
"id": "A.5.9",
"name": "Inventory of information and other associated assets",
"description": "An inventory of information and other associated assets, including owners, shall be developed and maintained."
},
{
"id": "A.5.10",
"name": "Acceptable use of information and other associated assets",
"description": "Rules for the acceptable use and procedures for handling information and other associated assets shall be identified, documented and implemented."
},
{
"id": "A.5.11",
"name": "Return of assets",
"description": "Personnel and other interested parties as appropriate shall return all the organization’s assets in their possession upon change or termination of their employment, contract or agreement."
},
{
"id": "A.5.12",
"name": "Classification of information",
"description": "Information shall be classified according to the information security needs of the organization based on confidentiality, integrity, availability and relevant interested party requirements."
},
{
"id": "A.5.13",
"name": "Labelling of information",
"description": "An appropriate set of procedures for information labelling shall be developed and implemented in accordance with the information classification scheme adopted by the organization."
},
{
"id": "A.5.14",
"name": "Information transfer",
"description": "Information transfer rules, procedures, or agreements shall be in place for all types of transfer facilities within the organization and between the organization and other parties."
},
{
"id": "A.5.15",
"name": "Access control",
"description": "Rules to control physical and logical access to information and other associated assets shall be established and implemented based on business and information security requirements."
},
{
"id": "A.5.16",
"name": "Identity management",
"description": "The full life cycle of identities shall be managed."
},
{
"id": "A.5.17",
"name": "Authentication information",
"description": "Allocation and management of authentication information shall be controlled by a management process, including advising personnel on the appropriate handling of authentication information."
},
{
"id": "A.5.18",
"name": "Access rights",
"description": "Access rights to information and other associated assets shall be provisioned, reviewed, modified and removed in accordance with the organization’s topic-specific policy on and rules for access control."
},
{
"id": "A.5.19",
"name": "Information security in supplier relationships",
"description": "Processes and procedures shall be defined and implemented to manage the information security risks associated with the use of supplier’s products or services."
},
{
"id": "A.5.20",
"name": "Addressing information security within supplier agreements",
"description": "Relevant information security requirements shall be established and agreed with each supplier based on the type of supplier relationship."
},
{
"id": "A.5.21",
"name": "Managing information security in the ICT supply chain",
"description": "Processes and procedures shall be defined and implemented to manage the information security risks associated with the ICT products and services supply chain."
},
{
"id": "A.5.22",
"name": "Monitoring, review and change management of supplier services",
"description": "The organization shall regularly monitor, review, evaluate and manage change in supplier information security practices and service delivery."
},
{
"id": "A.5.23",
"name": "Information security for use of cloud services",
"description": "Processes for acquisition, use, management and exit from cloud services shall be established in accordance with the organization’s information security requirements."
},
{
"id": "A.5.24",
"name": "Information security incident management planning and preparation",
"description": "The organization shall plan and prepare for managing information security incidents by defining, establishing and communicating information security incident management processes, roles and responsibilities."
},
{
"id": "A.5.25",
"name": "Assessment and decision on information security events",
"description": "The organization shall assess information security events and decide if they are to be categorized as information security incidents."
},
{
"id": "A.5.26",
"name": "Response to information security incidents",
"description": "Information security incidents shall be responded to in accordance with the documented procedures."
},
{
"id": "A.5.27",
"name": "Learning from information security incidents",
"description": "Knowledge gained from information security incidents shall be used to strengthen and improve the information security controls."
},
{
"id": "A.5.28",
"name": "Collection of evidence",
"description": "The organization shall establish and implement procedures for the identification, collection, acquisition and preservation of evidence related to information security events."
},
{
"id": "A.5.29",
"name": "Information security during disruption",
"description": "The organization shall plan how to maintain information security at an appropriate level during disruption."
},
{
"id": "A.5.30",
"name": "ICT readiness for business continuity",
"description": "ICT readiness shall be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements."
},
{
"id": "A.5.31",
"name": "Legal, statutory, regulatory and contractual requirements",
"description": "Legal, statutory, regulatory and contractual requirements relevant to information security and the organization’s approach to meet these requirements shall be identified, documented and kept up to date."
},
{
"id": "A.5.32",
"name": "Intellectual property rights",
"description": "The organization shall implement appropriate procedures to protect intellectual property rights."
},
{
"id": "A.5.33",
"name": "Protection of records",
"description": "Records shall be protected from loss, destruction, falsification, unauthorized access and unauthorized release."
},
{
"id": "A.5.34",
"name": "Privacy and protection of PII",
"description": "The organization shall identify and meet the requirements regarding the preservation of privacy and protection of PII according to applicable laws and regulations and contractual requirements."
},
{
"id": "A.5.35",
"name": "Independent review of information security",
"description": "The organization’s approach to managing information security and its implementation including people, processes and technologies shall be reviewed independently at planned intervals, or when significant changes occur."
},
{
"id": "A.5.36",
"name": "Compliance with policies, rules and standards for information security",
"description": "Compliance with the organization’s information security policy, topic-specific policies, rules and standards shall be regularly reviewed."
},
{
"id": "A.5.37",
"name": "Documented operating procedures",
"description": "Operating procedures for information processing facilities shall be documented and made available to personnel who need them."
},
{
"id": "A.6.1",
"name": "Screening",
"description": "Background verification checks on all candidates to become personnel shall be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations and ethics and be proportional to the business requirements, the classification of the information to be accessed and the perceived risks."
},
{
"id": "A.6.2",
"name": "Terms and conditions of employment",
"description": "The employment contractual agreements shall state the personnel’s and the organization’s responsibilities for information security."
},
{
"id": "A.6.3",
"name": "Information security awareness, education and training",
"description": "Personnel of the organization and relevant interested parties shall receive appropriate information security awareness, education and training and regular updates of the organization's information security policy, topic-specific policies and procedures, as relevant for their job function."
},
{
"id": "A.6.4",
"name": "Disciplinary process",
"description": "A disciplinary process shall be formalized and communicated to take actions against personnel and other relevant interested parties who have committed an information security policy violation"
},
{
"id": "A.6.5",
"name": "Responsibilities after termination or change of employment",
"description": "Information security responsibilities and duties that remain valid after termination or change of employment shall be defined, enforced and communicated to relevant personnel and other interested parties."
},
{
"id": "A.6.6",
"name": "Confidentiality or non-disclosure agreements",
"description": "Confidentiality or non-disclosure agreements reflecting the organization’s needs for the protection of information shall be identified, documented, regularly reviewed and signed by personnel and other relevant interested parties."
},
{
"id": "A.6.7",
"name": "Remote working",
"description": "Security measures shall be implemented when personnel are working remotely to protect information accessed, processed or stored outside the organization’s premises."
},
{
"id": "A.6.8",
"name": "Information security event reporting",
"description": "The organization shall provide a mechanism for personnel to report observed or suspected information security events through appropriate channels in a timely manner."
},
{
"id": "A.7.1",
"name": "Physical security perimeters",
"description": "Security perimeters shall be defined and used to protect areas that contain information and other associated assets."
},
{
"id": "A.7.2",
"name": "Physical entry",
"description": "Secure areas shall be protected by appropriate entry controls and access points."
},
{
"id": "A.7.3",
"name": "Securing offices, rooms and facilities",
"description": "Physical security for offices, rooms and facilities shall be designed and implemented."
},
{
"id": "A.7.4",
"name": "Physical security monitoring",
"description": "Premises shall be continuously monitored for unauthorized physical access."
},
{
"id": "A.7.5",
"name": "Protecting against physical and environmental threats",
"description": "Protection against physical and environmental threats, such as natural disasters and other intentional or unintentional physical threats to infrastructure shall be designed and implemented."
},
{
"id": "A.7.6",
"name": "Working in secure areas",
"description": "Security measures for working in secure areas shall be designed and implemented."
},
{
"id": "A.7.7",
"name": "Clear desk and clear screen",
"description": "Clear desk rules for papers and removable storage media and clear screen rules for information processing facilities shall be defined and appropriately enforced."
},
{
"id": "A.7.8",
"name": "Equipment siting and protection",
"description": "Equipment shall be sited securely and protected."
},
{
"id": "A.7.9",
"name": "Security of assets off-premises",
"description": "Off-site assets shall be protected."
},
{
"id": "A.7.10",
"name": "Storage media",
"description": "Storage media shall be managed through their life cycle of acquisition, use, transportation and disposal in accordance with the organization’s classification scheme and handling requirements."
},
{
"id": "A.7.11",
"name": "Supporting utilities",
"description": "Information processing facilities shall be protected from power failures and other disruptions caused by failures in supporting utilities."
},
{
"id": "A.7.12",
"name": "Cabling security",
"description": "Cables carrying power, data or supporting information services shall be protected from interception, interference or damage."
},
{
"id": "A.7.13",
"name": "Equipment maintenance",
"description": "Equipment shall be maintained correctly to ensure availability, integrity and confidentiality of information."
},
{
"id": "A.7.14",
"name": "Secure disposal or re-use of equipment",
"description": "Items of equipment containing storage media shall be verified to ensure that any sensitive data and licensed software has been removed or securely overwritten prior to disposal or re-use."
},
{
"id": "A.8.1",
"name": "User endpoint devices",
"description": "Information stored on, processed by or accessible via user endpoint devices shall be protected."
},
{
"id": "A.8.2",
"name": "Privileged access rights",
"description": "The allocation and use of privileged access rights shall be restricted and managed."
},
{
"id": "A.8.3",
"name": "Information access restriction",
"description": "Access to information and other associated assets shall be restricted in accordance with the established topic-specific policy on access control."
},
{
"id": "A.8.4",
"name": "Access to source code",
"description": "Read and write access to source code, development tools and software libraries shall be appropriately managed."
},
{
"id": "A.8.5",
"name": "Secure authentication",
"description": "Secure authentication technologies and procedures shall be implemented based on information access restrictions and the topic-specific policy on access control."
},
{
"id": "A.8.6",
"name": "Capacity management",
"description": "The use of resources shall be monitored and adjusted in line with current and expected capacity requirements."
},
{
"id": "A.8.7",
"name": "Protection against malware",
"description": "Protection against malware shall be implemented and supported by appropriate user awareness."
},
{
"id": "A.8.8",
"name": "Management of technical vulnerabilities",
"description": "Information about technical vulnerabilities of information systems in use shall be obtained, the organization’s exposure to such vulnerabilities should be evaluated and appropriate measures should be taken."
},
{
"id": "A.8.9",
"name": "Configuration management",
"description": "Configurations, including security configurations, of hardware, software, services and networks shall be established, documented, implemented, monitored and reviewed."
},
{
"id": "A.8.10",
"name": "Information deletion",
"description": "Information stored in information systems, devices or in any other storage media shall be deleted when no longer required."
},
{
"id": "A.8.11",
"name": "Data masking",
"description": "Data masking shall be used in accordance with the organization’s topic-specific policy on access control and other related topic-specific policies, and business requirements, taking applicable legislation into consideration."
},
{
"id": "A.8.12",
"name": "Data leakage prevention",
"description": "Data leakage prevention measures shall be applied to systems, networks and any other devices that process, store or transmit sensitive information."
},
{
"id": "A.8.13",
"name": "Information backup",
"description": "Backup copies of information, software and systems shall be maintained and regularly tested in accordance with the agreed topic-specific policy on backup."
},
{
"id": "A.8.14",
"name": "Redundancy of information processing facilities",
"description": "Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements."
},
{
"id": "A.8.15",
"name": "Logging",
"description": "Logs that record activities, exceptions, faults and other relevant events shall be produced, stored, protected and analysed."
},
{
"id": "A.8.16",
"name": "Monitoring activities",
"description": "Networks, systems and applications shall be monitored for anomalous behaviour and appropriate actions taken to evaluate potential information security incidents."
},
{
"id": "A.8.17",
"name": "Clock synchronization",
"description": "The clocks of information processing systems used by the organization shall be synchronized to approved time sources."
},
{
"id": "A.8.18",
"name": "Use of privileged utility programs",
"description": "The use of utility programs that can be capable of overriding system and application controls shall be restricted and tightly controlled."
},
{
"id": "A.8.19",
"name": "Installation of software on operational systems",
"description": "Procedures and measures shall be implemented to securely manage software installation on operational systems."
},
{
"id": "A.8.20",
"name": "Networks security",
"description": "Networks and network devices shall be secured, managed and controlled to protect information in systems and applications."
},
{
"id": "A.8.21",
"name": "Security of network services",
"description": "Security mechanisms, service levels and service requirements of network services shall be identified, implemented and monitored."
},
{
"id": "A.8.22",
"name": "Segregation of networks",
"description": "Groups of information services, users and information systems shall be segregated in the organization’s networks."
},
{
"id": "A.8.23",
"name": "Web filtering",
"description": "Access to external websites shall be managed to reduce exposure to malicious content."
},
{
"id": "A.8.24",
"name": "Use of cryptography",
"description": "Rules for the effective use of cryptography, including cryptographic key management, shall be defined and implemented."
},
{
"id": "A.8.25",
"name": "Secure development life cycle",
"description": "Rules for the secure development of software and systems shall be established and applied."
},
{
"id": "A.8.26",
"name": "Application security requirements",
"description": "Information security requirements shall be identified, specified and approved when developing or acquiring applications."
},
{
"id": "A.8.27",
"name": "Secure system architecture and engineering principles",
"description": "Principles for engineering secure systems shall be established, documented, maintained and applied to any information system development activities."
},
{
"id": "A.8.28",
"name": "Secure coding",
"description": "Secure coding principles shall be applied to software development."
},
{
"id": "A.8.29",
"name": "Security testing in development and acceptance",
"description": "Security testing processes shall be defined and implemented in the development life cycle."
},
{
"id": "A.8.30",
"name": "Outsourced development",
"description": "The organization shall direct, monitor and review the activities related to outsourced system development."
},
{
"id": "A.8.31",
"name": "Separation of development, test and production environments",
"description": "Development, testing and production environments shall be separated and secured."
},
{
"id": "A.8.32",
"name": "Change management",
"description": "Changes to information processing facilities and information systems shall be subject to change management procedures."
},
{
"id": "A.8.33",
"name": "Test information",
"description": "Test information shall be appropriately selected, protected and managed."
},
{
"id": "A.8.34",
"name": "Protection of information systems during audit testing",
"description": "Audit tests and other assurance activities involving assessment of operational systems shall be planned and agreed between the tester and appropriate management."
}
]
}

249
data/frameworks/SOC2.json Normal file
View File

@@ -0,0 +1,249 @@
{
"name": "SOC2",
"controls": [
{
"id": "CC1.1",
"name": "COSO Principle 1: The entity demonstrates a commitment to integrity and ethical values."
},
{
"id": "CC1.2",
"name": "COSO Principle 2: The board of directors demonstrates independence from management and exercises oversight of the development and performance of internal control."
},
{
"id": "CC1.3",
"name": "COSO Principle 3: Management establishes, with board oversight, structures, reporting lines, and appropriate authorities and responsibilities in the pursuit of objectives."
},
{
"id": "CC1.4",
"name": "COSO Principle 4: The entity demonstrates a individuals in alignment with objectives."
},
{
"id": "CC1.5",
"name": "COSO Principle 5: The entity holds individuals in the pursuit of objectives."
},
{
"id": "CC2.1",
"name": "COSO Principle 13: The entity obtains or generates functioning of internal control."
},
{
"id": "CC2.2",
"name": "COSO Principle 14: The entity internally communicates information, including objectives and responsibilities for internal control, necessary to support the functioning of internal control."
},
{
"id": "CC2.3",
"name": "COSO Principle 15: The entity communicates with functioning of internal control."
},
{
"id": "CC3.1",
"name": "COSO Principle 6: The entity specifies objectives with assessment of risks relating to objectives."
},
{
"id": "CC3.2",
"name": "COSO Principle 7: The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managed."
},
{
"id": "CC3.3",
"name": "COSO Principle 8: The entity considers the potential objectives."
},
{
"id": "CC3.4",
"name": "COSO Principle 9: The entity identifies and assesses internal control."
},
{
"id": "CC4.1",
"name": "COSO Principle 16: The entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning."
},
{
"id": "CC4.2",
"name": "COSO Principle 17: The entity evaluates and communicates internal control deficiencies in a timely corrective action, including senior management and the board of directors, as appropriate."
},
{
"id": "CC5.1",
"name": "COSO Principle 10: The entity selects and develops control activities that contribute to the mitigation of risks to the achievement of objectives to acceptable levels."
},
{
"id": "CC5.2",
"name": "COSO Principle 11: The entity also selects and support the achievement of objectives."
},
{
"id": "CC5.3",
"name": "COSO Principle 12: The entity deploys control activities through policies that establish what is expected and in procedures that put policies into action."
},
{
"id": "CC6.1",
"name": "The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity’s objectives."
},
{
"id": "CC6.2",
"name": "Prior to issuing system credentials and granting system access, the entity registers and authorizes new internal and external users whose access is administered by the entity. For those users whose access is administered by the entity, user system credentials are removed when user access is no longer authorized."
},
{
"id": "CC6.3",
"name": "The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes, giving consideration to the concepts of least privilege and segregation of duties, to meet the entity’s objectives."
},
{
"id": "CC6.4",
"name": "The entity restricts physical access to facilities and protected information assets (for example, data center locations) to authorized personnel to meet the entity’s objectives."
},
{
"id": "CC6.5",
"name": "The entity discontinues logical and physical protections over physical assets only after the ability to read or diminished and is no longer required to meet the entity’s objectives."
},
{
"id": "CC6.6",
"name": "The entity implements logical access security measures system boundaries."
},
{
"id": "CC6.7",
"name": "The entity restricts the transmission, movement, and removal of information to authorized internal and transmission, movement, or removal to meet the entity’s objectives."
},
{
"id": "CC6.8",
"name": "The entity implements controls to prevent or detect and software to meet the entity’s objectives."
},
{
"id": "CC7.1",
"name": "To meet its objectives, the entity uses detection and monitoring procedures to identify (1) changes to vulnerabilities, and (2) susceptibilities to newly discovered vulnerabilities."
},
{
"id": "CC7.2",
"name": "The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity’s ability to meet its objectives; anomalies are analyzed to determine whether they represent security events."
},
{
"id": "CC7.3",
"name": "The entity evaluates security events to determine whether they could or have resulted in a failure of the entity to meet its objectives (security incidents) and, if so, takes actions to prevent or address such failures."
},
{
"id": "CC7.4",
"name": "The entity responds to identified security incidents by executing a defined incident response program to understand, contain, remediate, and communicate security incidents, as appropriate."
},
{
"id": "CC7.5",
"name": "The entity identifies, develops, and implements activities to recover from identified security incidents."
},
{
"id": "CC8.1",
"name": "The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives."
},
{
"id": "CC9.1",
"name": "The entity identifies, selects, and develops risk business disruptions."
},
{
"id": "CC9.2",
"name": "The entity assesses and manages risks associated with vendors and business partners."
},
{
"id": "A1.1",
"name": "The entity maintains, monitors, and evaluates current processing capacity and use of system components capacity demand and to enable the implementation of additional capacity to help meet its objectives."
},
{
"id": "A1.2",
"name": "The entity authorizes, designs, develops or acquires, implements, operates, approves, maintains, and back-up processes, and recovery infrastructure to meet its objectives."
},
{
"id": "A1.3",
"name": "The entity tests recovery plan procedures supporting system recovery to meet its objectives."
},
{
"id": "C1.1",
"name": "The entity identifies and maintains confidential confidentiality."
},
{
"id": "C1.2",
"name": "The entity disposes of confidential information to meet the entity’s objectives related to confidentiality."
},
{
"id": "PI1.1",
"name": "The entity obtains or generates, uses, and communicates relevant, quality information regarding the objectives processed and product and service specifications, to support the use of products and services."
},
{
"id": "PI1.2",
"name": "The entity implements policies and procedures over system inputs, including controls over completeness and accuracy, to result in products, services, and reporting to meet the entity’s objectives."
},
{
"id": "PI1.3",
"name": "The entity implements policies and procedures over reporting to meet the entity’s objectives."
},
{
"id": "PI1.4",
"name": "The entity implements policies and procedures to make available or deliver output completely, accurately, and timely in accordance with specifications to meet the entity’s objectives."
},
{
"id": "PI1.5",
"name": "The entity implements policies and procedures to store inputs, items in processing, and outputs completely, accurately, and timely in accordance with system specifications to meet the entity’s objectives."
},
{
"id": "P1.1",
"name": "The entity provides notice to data subjects about its privacy practices to meet the entity’s objectives related to privacy. The notice is updated and communicated to entity’s privacy practices, including changes in the use of personal information, to meet the entity’s objectives related to privacy."
},
{
"id": "P2.1",
"name": "The entity communicates choices available regarding the collection, use, retention, disclosure, and disposal of personal information to the data subjects and the consequences, if any, of each choice. Explicit consent for the collection, use, retention, disclosure, and disposal of personal information is obtained from data subjects or other authorized persons, if required. Such consent is obtained only for the intended purpose of the information to meet the entity’s objectives related to privacy. The entity’s basis for determining implicit consent for the collection, use, retention, disclosure, and disposal of personal information is documented."
},
{
"id": "P3.1",
"name": "Personal information is collected consistent with the entity’s objectives related to privacy."
},
{
"id": "P3.2",
"name": "For information requiring explicit consent, the entity communicates the need for such consent, as well as the consequences of a failure to provide consent for the request for personal information, and obtains the consent prior to the collection of the information to meet the entity’s objectives related to privacy."
},
{
"id": "P4.1",
"name": "The entity limits the use of personal information to the privacy."
},
{
"id": "P4.2",
"name": "The entity retains personal information consistent with the entity’s objectives related to privacy."
},
{
"id": "P4.3",
"name": "The entity securely disposes of personal information to meet the entity’s objectives related to privacy."
},
{
"id": "P5.1",
"name": "The entity grants identified and authenticated data subjects the ability to access their stored personal information for review and, upon request, provides physical or electronic copies of that information to data subjects to meet the entity’s objectives related to privacy. If access is denied, data subjects are informed of the denial and reason for such denial, as required, to meet the entity’s objectives related to privacy."
},
{
"id": "P5.2",
"name": "The entity corrects, amends, or appends personal information based on information provided by data subjects and communicates such information to third parties, as committed or required, to meet the entity’s objectives related to privacy. If a request for correction is denied, data subjects are informed of the denial and reason for such denial to meet the entity’s objectives related to privacy."
},
{
"id": "P6.1",
"name": "The entity discloses personal information to third parties with the explicit consent of data subjects, and such consent is obtained prior to disclosure to meet the entity’s objectives related to privacy."
},
{
"id": "P6.2",
"name": "The entity creates and retains a complete, accurate, and timely record of authorized disclosures of personal information to meet the entity’s objectives related to privacy."
},
{
"id": "P6.3",
"name": "The entity creates and retains a complete, accurate, and timely record of detected or reported unauthorized information to meet the entity’s objectives related to privacy."
},
{
"id": "P6.4",
"name": "The entity obtains privacy commitments from vendors and other third parties who have access to personal information to meet the entity’s objectives related to privacy. The entity assesses those parties’ compliance on a periodic and as-needed basis and takes corrective action, if necessary."
},
{
"id": "P6.5",
"name": "The entity obtains commitments from vendors and other third parties with access to personal information to notify the entity in the event of actual or suspected unauthorized disclosures of personal information. Such notifications are reported to appropriate personnel and acted on in accordance with established incident response procedures to meet the entity’s objectives related to privacy."
},
{
"id": "P6.6",
"name": "The entity provides notification of breaches and others to meet the entity’s objectives related to privacy."
},
{
"id": "P6.7",
"name": "The entity provides data subjects with an accounting of the personal information held and disclosure of the subjects’ request, to meet the entity’s objectives related to privacy."
},
{
"id": "P7.1",
"name": "The entity collects and maintains accurate, up-to-date, the entity’s objectives related to privacy."
},
{
"id": "P8.1",
"name": "The entity implements a process for receiving, addressing, resolving, and communicating the resolution of inquiries, complaints, and disputes from data subjects and others and periodically monitors compliance to meet the entity’s objectives related to privacy. Corrections and other necessary actions related to identified deficiencies are made or taken in a timely manner."
}
]
}

365
data/frameworks/soc2.yaml
View File

@@ -1,365 +0,0 @@
framework:
name: soc2
description: SOC 2
content-ref: "8d133718-f74b-4393-b072-e5fc89bcb952"
controls:
- content-ref: "44be4eb5-ae65-4c84-b7ac-083979af3f64"
category: "Secure your offices and internet access"
importance: "MANDATORY"
standards: ["CC 6.4"]
name: "Implement Physical Access Control"
description: |
Even if you do most of your business online, you still have offices, computers or even printed document: you need to make sure those assets are physically secured (we will focus on the digital access later).
- content-ref: "c878ed70-01d3-4796-8572-0228ff6dda0c"
category: "Secure your offices and internet access"
name: "Use VPNs to Secure Access for Remote Devices"
importance: "PREFERRED"
standards: ["CC 6.4", "CC 6.6", "CC 6.7"]
description: |
In short, implementing a VPN will encrypt your data and ensure a safe transmission between your employees devices and your internal network (even when using untrusted networks like a public wifi) ⇒ it offers a layer of security for your data.
- content-ref: "4ebc26df-6a3e-47fa-8adb-42fb8f0f5703"
category: "Secure your offices and internet access"
name: "Cloud datacenter physical security"
importance: "PREFERRED"
standards: ["CC 6.4"]
description: |
You know how critical a data center is. You don’t want unauthorized people to access it.
- content-ref: "23590469-5569-4d13-8f13-89de55f7cc77"
category: "Secure your offices and internet access"
name: "Implement Visitor Access Policies"
importance: "MANDATORY"
standards: ["CC 6.4"]
description: |
Even if you do most of your business online, you still have offices, computers or even printed document: you need to make sure those assets are physically secured (we will focus on the digital access later) regarding visitors.
- content-ref: "07402b58-762f-4a8d-a08b-dfddf7beca6c"
category: "Manage your computers"
name: "Protect your employees devices"
importance: "MANDATORY"
standards:
["CC 2.1", "CC 6.1", "CC 6.6", "CC 6.7", "CC 6.8", "CC 7.1", "CC 7.2"]
description: |
Mobile devices often have access to sensitive company data ⇒ you need to ensure that all devices are secure and compliant with established security policies.
- content-ref: "edef4ee7-01bf-43df-a815-ce1862e6fef1"
category: "Set up your employees for success"
name: "Integrate security checklist in your onboarding process"
importance: "MANDATORY"
standards: ["CC 1.4", "CC 5.3"]
description: |
It is the perfect timing to ensure that every employees has:
- accepted and signed all documents
- the access needed to perform his/her tasks
- started his/her security training
- content-ref: "578170a0-e0a5-47ef-9fdb-6971deee2958"
category: "Set up your employees for success"
name: "Properly off-board your employees"
importance: "MANDATORY"
standards: ["CC 5.3", "CC 6.2", "CC 6.5"]
description: |
Yes, people will leave your company (either by your decision or theirs). And you want to be prepare! If an early employee leaves and you forgot to change the ownership on his/her document, you might lose the documents.
Also, you want to be sure people can’t access the company data or systems once they left!
- content-ref: "03e71306-95dc-4e59-9e35-71dba7b2a831"
category: "Set up your employees for success"
name: "Know your recruits"
importance: "MANDATORY"
standards: ["CC 1.4"]
description: |
When recruiting someone, you want to be sure of who you are hiring: by performing reference checks (it can also be background checks), you add an additional layer of certainty on the candidate by looking for potential red flags in the candidate’s past (history of unethical behavior, harassment, fraud, etc..).
- content-ref: "1bf9192a-1b6a-48da-b232-a6e01c0c4e06"
category: "Set up your employees for success"
name: "Train your employees on security"
importance: "PREFERRED"
standards: ["CC 1.4", "CC 2.2"]
description: |
Your employees are the main target of cyber threats (especially phishing and social engineering), and education is one of the best way to reduce risk. Awareness of your employees will improve your company security.
- content-ref: "0296ff7e-f57a-4e68-abad-1146b7b8311b"
category: "Set up your employees for success"
name: "Implement confidential whistleblower process"
importance: "ADVANCED"
standards: ["CC 2.2"]
description: |
It encourages and enables employees to raise serious concerns (violations of your code of ethics or law or regulations) in order for them to be addressed and corrected while being protected from any retaliation.
- content-ref: "dfd5fa7a-db83-4c34-b21f-846e7775c594"
category: "Set up your employees for success"
name: "Run performance reviews"
importance: "PREFERRED"
standards: ["CC 1.3", "CC 1.4", "CC 1.5", "CC 4.2", "CC 5.3"]
description: |
Makes sure your team has the skills and focus needed to protect what matters most in your business. They help spot training gaps, reinforce accountability and ensure everyone is aligned with your operational goals - security being one of them. It's all about building a culture that proactively minimizes risks while continuously improving.
- content-ref: "ce18a430-13af-4c76-9e43-816877e82ddd"
category: "Set up your employees for success"
name: "Specify security responsabilities"
importance: "MANDATORY"
standards: ["CC 1.3", "CC 1.4", "CC 2.2", "CC 5.3", "CC 1.2"]
description: |
Having clear ownership improve accountability, it helps employees figure out what is legit and what is not.
- content-ref: "08df0530-0d7e-430c-9a1d-c97db46e2c66"
category: "Secure your emails"
name: "Implement email filtering and warning system"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.8"]
description: |
As you know ⇒ email is the most common entry point. Each phishing email filtered out of your employee mailbox is less mental load for you and your employees and less risk faced by your company.
- content-ref: "25fa20e1-0772-4103-8d57-24da3d59f7d1"
category: "Secure your emails"
name: "Implement email authentication (DMARC)"
importance: "PREFERRED"
standards: ["CC 6.8", "CC 7.2"]
description: |
DMARK (Domain-based Message Authentication, Reporting, and Conformance) helps prevent email spoofing and phishing attacks by verifying the authenticity of emails sent from your domain.
It will do two things:
- your recipient will know for sure it is coming from you and it will protect your company reputation (with gmail and cie).
- you will be sure (if activated) that the email you received is really from the said company (if they parametered DMARC as well)
- content-ref: "54dcea24-d714-46a7-8e8e-3967a8dad962"
category: "Secure your emails"
name: "Quarantine suspicious emails"
importance: "ADVANCED"
standards: ["CC 6.8", "CC 7.2"]
description: |
If you set up email quarantine in Google Workspace, you prevent potentially harmful emails from reaching your employees. By following the steps below, you can create customized rules to catch and review spam, phishing attempts, and malicious content, ensuring a more secure email environment.
- content-ref: "e8c50ebe-a395-40df-b1d6-54d4020babcc"
category: "Configure your system access"
name: "Enable 2FA on critical services"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.8"]
description: |
In order to minimize the threat of someone getting access to something they should not, we follow the **secure principle:** nobody can easily get access to data/systems.
We need to ensure that if someone has access to your password, they still cannot log into your account. Multi-Factor Authentication (MFA) adds extra layers of security by requiring users to provide additional authentication factors beyond their passwords. The most standard solution is 2FA: your password + something else.
- content-ref: "51e1ae1f-fe5b-4c65-bc0f-cd90a156437e"
category: "Configure your system access"
name: "Setup slack channel for access request"
importance: "MANDATORY"
standards: ["CC 6.2", "CC 6.3"]
description: |
In order to minimize the threat of someone getting access to something they should not, we follow the continuous update principle: making sure the privileges are up to date. We need to setup a proper process to define how we grant and revoke access to different systems.
- content-ref: "4f2b2e96-50a2-465f-8c31-85db878a402c"
category: "Configure your system access"
name: "Setup a password manager"
importance: "PREFERRED"
standards: ["CC 6.1"]
description: |
In order to minimize the threat of someone getting access to something they should not, we want to ensure a few things:
- The password used in your company are complex enough
- They are stored encrypted
- They are shared safely when needed (not openly, on slack or by text)
- They are not compromised
The easiest way to implement those is to use a password manager.
- content-ref: "077349b3-5df1-44eb-9c8e-3b3d291c0199"
category: "Configure your system access"
name: "Setup role based access (RBAC)"
importance: "PREFERRED"
standards: ["CC 2.1", "CC 6.1"]
description: |
In order to minimize the threat of someone getting access to something they should not, we follow the least privilege principle: access is limited to what's necessary for job duties. We need to define which function should have access to which tool in your company to serve as a reference when providing access to people (password manager vaults etc.).
- content-ref: "0245ebe5-7108-4fc6-b64f-96e0e0b24f67"
category: "Configure your system access"
name: "Enforce SSO when possible"
importance: "PREFERRED"
standards: ["CC 6.1"]
description: |
To minimize the risk of unauthorized access, it's important to centralize and secure authentication across your organization. Single Sign-On (SSO) enhances security by enabling better control over account access, enforcing consistent security policies (e.g., 2FA), and making it easier to revoke access when someone leaves the organization.
- content-ref: "66fabe67-82d1-4957-af81-c4b89485212a"
category: "Secure your codebase"
name: "Require Pull Requests (PRs)"
importance: "MANDATORY"
standards: ["CC 1.4", "CC 8.1", "CC 5.2"]
description: |
Requiring pull requests and code reviews ensures higher code quality and security by allowing multiple team members to catch bugs, inefficiencies, and potential vulnerabilities before code is merged. It also promotes collaboration, knowledge sharing, and accountability within the team. This process helps prevent issues in production and maintains adherence to coding standards.
- content-ref: "a1fcbc72-de61-47c1-b65d-cbc7c75c158d"
category: "Secure your codebase"
name: "Set-up dependancy vulnerability alerts"
importance: "MANDATORY"
standards: ["CC 4.1", "CC 8.1"]
description: |
It ensures your project stays secure and up-to-date without manual tracking of dependencies. It also reduces the risk of using outdated or insecure libraries in your codebase.
- content-ref: "2bb3102d-6bc7-4869-a86d-3ee2e6cb7756"
category: "Secure your codebase"
name: "Set-up 2FA for all contributors"
importance: "MANDATORY"
standards: ["CC 5.2"]
description: |
It reduces the risk of account compromise for all contributors, especially the ones not in your company.
- content-ref: "515c6c80-2274-40f0-82cd-cc912a2be1f9"
category: "Secure your codebase"
name: "Enable code scanning"
importance: "PREFERRED"
standards: ["CC 4.1", "CC 8.1"]
description: |
It ensures that potential security flaws are detected early. This proactive approach strengthens your security posture and helps maintain high code quality.
- content-ref: "f88963fe-2641-47b7-8a03-f18704952024"
category: "Secure your codebase"
name: "Document your development lifecycle"
importance: "PREFERRED"
standards: ["CC 1.4", "CC 5.2", "CC 8.1"]
description: |
Formalizing a proper development lifecycle helps your engineer in their jobs and helps you to scale your team. It reduces the chances of human error.
- content-ref: "8a5d46b7-ece7-4f84-b720-ccf88c5d49f8"
category: "Secure your infrastructure"
name: "List of your assets"
importance: "MANDATORY"
standards: ["CC 2.1", "CC 4.1"]
description: |
The assets that are storing or processing data are potential vulnerabilities that could be exploited. ⇒ You need to know which assets your company has in order to be able to properly manage and secure them.
- content-ref: "6a8a1745-850b-44ee-a688-d3e126ad46fa"
category: "Secure your infrastructure"
name: "Scan for Security updates"
importance: "MANDATORY"
standards: ["CC 4.1", "CC 6.8", "CC 7.1"]
description: |
An automated security scanning software on your infrastructure components enables you to fix potential vulnerabilities as soon as they are uncovered.
- content-ref: "5c18790f-f0f6-41ce-ae4b-6f6b3bcb7058"
category: "Secure your infrastructure"
name: "Implement IAM for database authentication"
importance: "PREFERRED"
standards: ["CC 6.1"]
description: |
You want to ensure that only the proper people can access your production database. You also want to avoid the burden of managing another list of users or rotating credentials.
- content-ref: "3274441b-b8b9-44ea-bd2a-bc2652b48973"
category: "Secure your infrastructure"
name: "Plug GCP & Github"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.8 6.3"]
description: |
Having credentials to manage can become a nightmare (especially if you need to change/rotate them often) - it quickly becomes time consuming. It is the same with lifetime tokens - someone leaving and you need to change them.
- content-ref: "b0c11cc1-07f4-43ab-badb-e6ebf0cd9152"
category: "Secure your infrastructure"
name: "Manage your service accounts"
importance: "MANDATORY"
standards: ["CC 6.3"]
description: |
You don’t want to use the “default” service account, it has way too many permissions - it is a super administrator. Even GCP is asking you not to use it, it is only here for legacy reasons. In the same idea, grant your service accounts only what is necessary.
- content-ref: "cd865af6-0ab8-4366-b4eb-fb84baf03a87"
category: "Secure your infrastructure"
name: "Keep an history of all your changes"
importance: "MANDATORY"
standards: ["CC 7.1", "CC 7.2", "CC 8.1", "CC 5.3"]
description: |
Infrastructure as Code (IaC) makes sure all your infrastructure changes are done in a standardized and repeatable process - the chance of human error is lower. Moreover, IaC enables version control and peer reviews. When growing, you will have to do it - the earlier the better (later, it can become really painful).
- content-ref: "2553b667-5abd-426f-adc4-e9824e8d0994"
category: "Secure your infrastructure"
name: "Streamline your patch management"
importance: "MANDATORY"
standards: ["CC 7.1"]
description: |
New OS version vulnerabilities are regularly discovered - not applying patches for those leaves your application “open” to a publicly known vulnerability. If you don’t streamline the process, it will requires investment on your side and increase the exposure duration.
- content-ref: "c152fa68-0c76-405c-b07c-8fb413af06d0"
category: "Protect your Network"
name: "Restrict public access on your infrastructure"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.6", "CC 6.7"]
description: |
Public access to your company's infrastructure is a serious security risk. By configuring your cloud provider to restrict public access, you can reduce the risk of unauthorized access to your sensitive data and systems.
- content-ref: "f68a9024-44b1-4bdd-b659-b086ff5865a4"
category: "Protect your Network"
name: "Set-up a WAF"
importance: "PREFERRED"
standards: ["CC 6.1", "CC 6.6"]
description: |
Cloudflare filters malicious traffic, preventing attacks (like SQL injections and cross-site scripting) and mitigates risks of service disruptions. Additionally, Cloudflare can masks your origin IP, reducing exposure and limiting direct access to your infrastructure.
- content-ref: "845e0d1e-ee55-4b7d-80dd-ea333818e61e"
category: "Protect your Network"
name: "Run a penetration test"
importance: "ADVANCED"
standards: ["CC 3.2", "CC 4.1", "CC 8.1"]
description: |
It is a good way to safeguard your company’s data. It is a real-life simulation of attack scenarios on your company: it enables you to identify potential vulnerabilities that can be fixed before being exploited.
- content-ref: "1c3819b4-3f2c-4480-ad97-2a7b0283f8d8"
category: "Safeguard your data"
name: "Automated backup"
importance: "MANDATORY"
standards: ["CC 7.5", "CC 9.1"]
description: |
Automated backups ensure that your data - one of your company’s most important assets - is regularly and securely saved, reducing the risk of data loss. The back-up keep it safe and available, the automated and regular allows for a restoration just before any disruption, minimizing loss.
- content-ref: "f3395da7-b717-46b4-8092-9fca304c8344"
category: "Safeguard your data"
name: "Help the auditor with a data-flow diagram"
importance: "MANDATORY"
standards: ["CC 2.1", "CC 2.2"]
description: |
The auditor doesn’t know your company and your systems. Providing him with a diagram that show all account data accross your systems & networks will enable him/her to understand your challenges faster and also to better evaluate your tradeoffs (when needed). It will also help you be 100% clear on how you process your data, and help with onboarding.
- content-ref: "5d9fb42c-7d7b-466a-85b1-afb535dbf4a6"
category: "Safeguard your data"
name: "Encrypt your data storage"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.6", "CC 6.7"]
description: |
By encrypting data, you ensure that loss or theft of a device won’t result in a data breach. It also protects sensitive information from unauthorized access.
- content-ref: "44816697-458b-4768-9821-1e90325f0558"
category: "Safeguard your data"
name: "Encrypt your data in transit"
importance: "MANDATORY"
standards: ["CC 6.1", "CC 6.6", "CC 6.7"]
description: |
Data sent over networks can be intercepted and read - the encryption ensure it won’t be intelligible. It secure it from potential threats.
- content-ref: "0c650a10-8407-4035-bcb1-6f4cd035122b"
category: "Safeguard your data"
name: "Data inventory"
importance: "MANDATORY"
standards: ["CC 2.1", "CC 6.1", "CC 9.2"]
description: |
Having an accurate and up-to-date inventory of all your data assets (databases, cloud storage or even file shares) enables you to be exhaustive in how you treat your data safety.
- content-ref: "32d8584d-d171-43e2-8428-b52cf0b5ad0d"
category: "Log collection and monitoring"
name: "Configure logs and implement real-time monitoring"
importance: "MANDATORY"
standards:
["CC 2.1", "CC 6.1", "CC 6.6", "CC 6.8", "CC 7.1", "CC 7.2", "CC 7.3"]
description: |
It allows you to detect and respond to potential security incidents or system failures immediately, minimizing downtime and reducing the risk of data breaches. It maintain visibility into system performance and security events.
- content-ref: "99b96e82-f750-4bca-85cc-860dcc681298"
category: "Log collection and monitoring"
name: "Keep your logs"
importance: "MANDATORY"
standards: ["CC 7.3"]
description: |
Logs help you to detect and investigate security incidents and troubleshoot operational issues. They provide an audit trail.
- content-ref: "0c384a4d-da22-4a90-ba0f-a83812a17f49"
category: "Log collection and monitoring"
name: "Be automatically notified of issues"
importance: "MANDATORY"
standards: ["6.1", "6.6", "6.8", "CC 7.1", "CC 7.2", "CC 7.3"]
description: |
Setting up alerting allows you to respond quickly and minimize downtime or potential data breaches. It ensures that important events, such as unauthorized access or system failures, are addressed promptly.
- content-ref: "c3fb8a93-4be5-44da-bcbc-8ee01cb31d2e"
category: "Prepare for incidents"
name: "Build an incident response process"
importance: "MANDATORY"
standards: ["CC 2.2"]
description: |
An incident response plan is crucial for quickly identifying, containing, and resolving incidents, minimizing potential disruptions. It ensures you’re prepared effectively and that you keep your operations running smoothly, even in the face of unexpected threats.
- content-ref: "07659ea9-7fce-4557-932e-49384b01bc10"
category: "Prepare for incidents"
name: "Create & test your disaster recovery plan"
importance: "MANDATORY"
standards: ["CC 3.2", "CC 5.1", "CC 7.5", "CC 8.1"]
description: |
Disasters might seem far-fetched, but data loss, service outages, and misconfigurations can happen. Whether it's a simple human error or a regional outage, a DRP helps your team recover fast and maintain customer trust.
- content-ref: "3745b7c3-d5ac-45da-80a5-3cf2009bd946"
category: "Share your SOC 2"
name: "Have a security page"
importance: "MANDATORY"
standards: ["CC 2.3"]
description: |
Having SOC-2 for yourself is useless, you want to leverage it as much as possible.
- content-ref: "be4808c3-8b1e-4d0a-a936-b067716d88e1"
category: "Share your SOC 2"
name: "Clearly explain your services"
importance: "MANDATORY"
standards: ["CC 2.3"]
description: |
Here, we are not enhancing security, we are helping the auditor be more efficient. As part of the audit, he/she will need to understand clear boundaries for the audit, identify the relevant risk and then check how you mitigate them.
A proper service description is key for your customers, but it also help the auditor understands what your customers are expecting from you.
- content-ref: "83a018c0-1031-4637-b9ca-7210330be626"
category: "Share your SOC 2"
name: "External support available"
importance: "PREFERRED"
standards: ["CC 2.3"]
description: |
External support is not required for SOC 2, but it enhances transparency by showcasing your security practices, policies, and compliance efforts, building trust with customers and stakeholders. - Ultimately, this is what SOC 2 is about: reassuring your prospect and customer on how you work.