{"id":40063,"date":"2026-06-10T14:53:30","date_gmt":"2026-06-10T12:53:30","guid":{"rendered":"https:\/\/kymos.com\/?page_id=40063"},"modified":"2026-06-10T15:08:53","modified_gmt":"2026-06-10T13:08:53","slug":"information-security-policy","status":"publish","type":"page","link":"https:\/\/kymos.com\/ko\/information-security-policy\/","title":{"rendered":"Information Security Policy"},"content":{"rendered":"<p><div class=\"fusion-fullwidth fullwidth-box fusion-builder-row-1 fusion-flex-container hundred-percent-fullwidth non-hundred-percent-height-scrolling\" style=\"--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-flex-wrap:wrap;\" ><div class=\"fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-justify-content-center fusion-flex-content-wrap\" style=\"width:calc( 100% + 20px ) !important;max-width:calc( 100% + 20px ) !important;margin-left: calc(-20px \/ 2 );margin-right: calc(-20px \/ 2 );\"><div class=\"fusion-layout-column fusion_builder_column fusion-builder-column-0 fusion_builder_column_1_1 1_1 fusion-flex-column\" style=\"--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:10px;--awb-margin-bottom-large:20px;--awb-spacing-left-large:10px;--awb-width-medium:100%;--awb-order-medium:0;--awb-spacing-right-medium:10px;--awb-spacing-left-medium:10px;--awb-width-small:100%;--awb-order-small:0;--awb-spacing-right-small:10px;--awb-spacing-left-small:10px;\"><div class=\"fusion-column-wrapper fusion-column-has-shadow fusion-flex-justify-content-flex-start fusion-content-layout-column\"><div class=\"fusion-title title fusion-title-1 fusion-sep-none fusion-title-center fusion-title-text fusion-title-size-one\"><h1 class=\"fusion-title-heading title-heading-center\" style=\"margin:0;\">Information Security Policy<\/h1><\/div><\/div><\/div><\/div><\/div><div class=\"fusion-fullwidth fullwidth-box fusion-builder-row-2 fusion-flex-container fusion-parallax-none nonhundred-percent-fullwidth non-hundred-percent-height-scrolling lazyload\" style=\"--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-margin-bottom:100px;--awb-min-height:350px;--awb-background-size:cover;--awb-flex-wrap:wrap;\" data-bg=\"https:\/\/kymos.com\/wp-content\/uploads\/2021\/07\/KYMOS-FACILITIES_GMP_GLP-Archive_20210623-BCN-0484-1.jpg\" ><div class=\"fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-content-wrap\" style=\"max-width:calc( 1170px + 20px );margin-left: calc(-20px \/ 2 );margin-right: calc(-20px \/ 2 );\"><\/div><\/div><div class=\"fusion-fullwidth fullwidth-box fusion-builder-row-3 fusion-flex-container nonhundred-percent-fullwidth non-hundred-percent-height-scrolling\" style=\"--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-padding-bottom:100px;--awb-margin-bottom:100px;--awb-flex-wrap:wrap;\" ><div class=\"fusion-builder-row fusion-row fusion-flex-align-items-flex-start fusion-flex-content-wrap\" style=\"max-width:calc( 1170px + 20px );margin-left: calc(-20px \/ 2 );margin-right: calc(-20px \/ 2 );\"><div class=\"fusion-layout-column fusion_builder_column fusion-builder-column-1 fusion_builder_column_1_1 1_1 fusion-flex-column\" style=\"--awb-bg-blend:overlay;--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:10px;--awb-margin-bottom-large:0px;--awb-spacing-left-large:10px;--awb-width-medium:100%;--awb-spacing-right-medium:10px;--awb-spacing-left-medium:10px;--awb-width-small:100%;--awb-spacing-right-small:10px;--awb-spacing-left-small:10px;\"><div class=\"fusion-column-wrapper fusion-flex-justify-content-flex-start fusion-content-layout-column\"><div class=\"fusion-text fusion-text-1\"><h2>1. Explanatory Memorandum<\/h2>\n<h1><a name=\"_Toc44501001\"><\/a><\/h1>\n<p>KYMOS depends on ICT (Information and Communications Technology) systems to achieve its objectives.<\/p>\n<p>These systems must be managed diligently, taking appropriate measures to protect them against accidental or deliberate damage that could affect the availability, integrity and confidentiality of the information processed or services provided.<\/p>\n<p>The objective of information security is to ensure the quality of information and the continued provision of services, acting preventively, monitoring daily activity and reacting promptly to incidents.<\/p>\n<p>To defend against these threats, a strategy that adapts to changing environmental conditions is required to ensure the continued provision of services.<\/p>\n<p>This implies that departments must implement the security measures required by <strong>ISO 27001 and the NIS 2 Directive (Annex I, point 5 \u201cHealth Sector\u201d, in conjunction with NACE Rev.2, Section C, point 21 \u201cManufacturing of medicine\u201d)<\/strong>, as well as continuously monitor service delivery levels, track, analyse and correct reported vulnerabilities, and prepare an effective incident response to ensure continuity of services provided.<\/p>\n<p>The different departments must ensure that ICT security is an integral part of every stage of the system&#8217;s lifecycle, from its conception to its decommissioning, through development or procurement decisions and operational activities.<\/p>\n<p>Security requirements and funding need to be identified and included in planning, request for tenders, and tender documents for ICT projects. Departments need to be prepared to prevent, detect, react and recover from incidents in accordance with NIS2 Directive in its article 29.a.<\/p>\n<h2>2. Security Incident Management<\/h2>\n<h1><a name=\"_Toc44501002\"><\/a><\/h1>\n<h3>2.1 Prevention<\/h3>\n<h2><a name=\"_Toc44501003\"><\/a><\/h2>\n<p>Departments must avoid, or at least prevent as far as possible, information or services from being compromised by security incidents. Both ISO 27001 and the NIS2 Directive state that systems must be designed and configured to ensure security by default, in line with the &#8220;Need to Know&#8221; least privilege policy.<\/p>\n<p>To this end, departments must implement the minimum-security measures determined by ISO 27001, in accordance with the requirements stated in NIS2 Directive, as well as any additional controls identified through a threat and risk assessment. These controls, together with the security roles and responsibilities of all personnel, must be clearly defined and documented.<\/p>\n<p>To ensure compliance with the policy, departments must:<\/p>\n<ul>\n<li>Establish secure areas for critical or confidential information systems.<\/li>\n<li>Authorise systems before going into operation.<\/li>\n<li>Regularly assess security, including assessments of configuration changes made on a daily basis.<\/li>\n<li>Request periodic review by third parties in order to obtain an independent assessment.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501004\"><\/a><a name=\"_Toc1923559608\"><\/a>2.2 Detection<\/h3>\n<p>As services can degrade rapidly due to incidents, ranging from a simple slowdown to a standstill, services must monitor the operation on a continuous basis to detect anomalies in service delivery levels and act accordingly as set out in ISO 27001 and NIS 2.<\/p>\n<p>Monitoring is particularly relevant when establishing lines of defence. Detection, analysis and reporting mechanisms shall be established that reach those responsible on a regular basis and when there is a significant deviation from parameters that have been pre-established as normal.<\/p>\n<p>Intrusion detection systems primarily monitor and audit the organisation&#8217;s resources, verifying that security policy is not violated and attempting to identify any malicious activity early and effectively.<\/p>\n<p>The following classifications will have to be established according to needs:<\/p>\n<ul>\n<li>Intrusion detection systems at network level.<\/li>\n<li>Intrusion detection systems at system level.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501005\"><\/a><a name=\"_Toc1722597330\"><\/a>2.3 Response<\/h3>\n<p>Departments must:<\/p>\n<ul>\n<li>Establish mechanisms to respond effectively to security incidents.<\/li>\n<li>Designate a point of contact for communications regarding incidents detected in other departments or other agencies.<\/li>\n<li>Establish protocols for the exchange of information related to the incident.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501006\"><\/a><a name=\"_Toc1556764919\"><\/a>2.4 Recovery<\/h3>\n<p>To ensure the availability of critical services, the organisation will ensure the existence of a continuity plan and related recovery activities.<\/p>\n<h2><a name=\"_Toc929768216\"><\/a>3. Scope<\/h2>\n<p>This policy applies to the information systems that support the analysis, quality control and certification of pharmaceutical, biotechnological and cosmetic products managed by Kymos Group.<\/p>\n<h2><a name=\"_Toc44501008\"><\/a><a name=\"_Toc2104540369\"><\/a>4. Mission and Services Provided<\/h2>\n<p>KYMOS, as a private company, looks after the management of its interests and within the scope of the provision of its services for the Public Administration and\/or Private Companies in the pharmaceutical sector, serves with objectivity the general interests by providing services that contribute to satisfy the needs of the services provided.<\/p>\n<h2><a name=\"_Toc44501009\"><\/a><a name=\"_Toc1199845148\"><\/a>5. Regulatory Framework<\/h2>\n<p>The legal framework for information security is established by the following:<\/p>\n<ul>\n<li>ISO\/IEC 27001:2022, Information security, cybersecurity and privacy protection.<\/li>\n<li>Directive (EU) 2022\/2555 of the European Parliament and of the Council of 14 December 2022 on measures to ensure a high common level of cybersecurity throughout the Union (NIS 2) and local implementing legislation.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501011\"><\/a><a name=\"_Toc1903222612\"><\/a>5.1 Protection of Personal Data<\/h3>\n<ul>\n<li>Regulation (EU) 2016\/679 of the European Parliament and of the Council of 27 April 2016 on the protection of individuals with regard to the processing of personal data and on the free movement of such data and repealing Directive 95\/46\/EC (General Data Protection Regulation).<\/li>\n<li>Law 3\/2018, of 5 December, on the Protection of Personal Data and Guarantee of Digital Rights.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501012\"><\/a><a name=\"_Toc573103810\"><\/a>5.2 E-Government and Electronic Signature<\/h3>\n<ul>\n<li>Regulation (EU) No. 910\/2014 of the European Parliament and of the Council (Electronic identification and trust services for electronic transactions in the internal market).<\/li>\n<li>Law 6\/2020, of 11 November, regulating certain aspects of electronic trust services.<\/li>\n<li>COM (2001) 298 &#8211; final, of the European Commission &#8211; Network and Information Security: Proposal for a European Policy Approach.<\/li>\n<li>Law 6\/2020, of 11 November, regulating certain aspects of electronic trust services.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501014\"><\/a><a name=\"_Toc2037824569\"><\/a>5.3 Network and Information Security<\/h3>\n<ul>\n<li>OECD Guidelines for the security of information systems and networks. Towards a culture of security. As a complement to current legislation, there is currently the international standard UNE ISO\/IEC 27002 &#8220;Code of Good Practice for information security management&#8221;, which has become a standard for auditing aspects related to information security in organisations.<\/li>\n<\/ul>\n<h2><a name=\"_Toc95368441\"><\/a><a name=\"_Toc44501015\"><\/a>6. Security Organisation: <a name=\"_Toc44501016\"><\/a>Committees Roles and Responsibilities<\/h2>\n<p>The Security Committee is the body that coordinates information security at the organisational level.<\/p>\n<p>It shall consist of the Information Security Officer and representatives from other areas affected by ISO 27001 and NIS2.<\/p>\n<p><a name=\"_Toc44501017\"><\/a><strong><u>Associated Functions and Responsibilities<\/u><\/strong><\/p>\n<ul>\n<li>Responsibilities derived from the processing of personal data, supporting the Data Protection Officer (DPO) in his or her functions.<\/li>\n<li>Addressing the concerns of the competent higher bodies and the different departments.<\/li>\n<li>Regularly report on the status of information security to the relevant higher-ups.<\/li>\n<li>Promote continuous improvement of the Information Security Management System (ISMS).<\/li>\n<li>Develop the organisation&#8217;s strategy for the evolution of information security.<\/li>\n<li>Coordinate the efforts of the different areas in relation to information security, to ensure that efforts are consistent, aligned with the strategy decided on in this area, and to avoid duplication.<\/li>\n<li>Develop (and regularly review) the Information Security Policy.<\/li>\n<li>Approve information security internal regulations.<\/li>\n<li>Develop and approve training and qualification requirements for administrators, operators and users from an information security point of view.<\/li>\n<li>Monitor the main residual risks assumed by the organisation and recommend possible actions to be taken.<\/li>\n<li>Monitor the performance of security incident management processes and recommend possible actions in this respect. In particular, ensure the coordination of the different security areas in the management of information security incidents.<\/li>\n<li>Promote periodic audits to verify compliance with the organisation&#8217;s security obligations.<\/li>\n<li>Approve plans to improve the organisation&#8217;s information security.<\/li>\n<li>Ensure that information security is taken into account in all projects from their initial specification to their implementation.<\/li>\n<li>Resolve conflicts of responsibility that may arise between the different people in charge and\/or between different areas of the organisation, communicating the situation to higher-ups those cases in which it does not have sufficient authority to decide.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501018\"><\/a><a name=\"_Toc1787269607\"><\/a><u>In the event of an information security incident<\/u><\/h3>\n<p>It shall approve the Security Improvement Plan, with its corresponding budget allocation. The Information Security Committee is not a technical committee, but it shall regularly seek from its own or external technical staff relevant information for decision-making. The Information Security Committee shall take advice on matters on which it has to decide or give an opinion. This advice shall be determined on a case-by-case basis and may take different forms and shapes:<\/p>\n<ul>\n<li>Internal, external or mixed specialised working groups.<\/li>\n<li>External consultancy.<\/li>\n<li>Attendance at courses or other types of training or experience-sharing environments.<\/li>\n<\/ul>\n<p>The Information Security Officer is the secretary of the Information Security Committee and as such:<\/p>\n<ul>\n<li>Convenes the meetings of the Information Security Committee.<\/li>\n<li>Prepares the topics to be discussed at Committee meetings, providing timely information for decision-making.<\/li>\n<li>It elaborates the minutes of the meetings.<\/li>\n<li>It is responsible for the direct or delegated implementation of the Committee&#8217;s decisions.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501019\"><\/a><a name=\"_Toc1697509853\"><\/a>6.1 Role definition<\/h3>\n<p>The Security Policy must identify those clearly responsible for ensuring compliance and must be known by all members of the administrative organisation.<\/p>\n<p>The following roles are established in the organisation related to Information Security.<\/p>\n<h4><a name=\"_Toc876861215\"><\/a>6.1.1 <u>Information Manager<\/u><\/h4>\n<p>It corresponds to the level of a top-level governing body which understands the mission of the organisation, determines the objectives it intends to achieve and is responsible for ensuring that they are achieved.<\/p>\n<p>Their functions may be assigned to a natural person or by the Information Security Committee.<\/p>\n<p>The person or body that undertakes it shall be identified for each Information handled by the organisation.<\/p>\n<h4><a name=\"_Toc44501021\"><\/a>Associated Functions and Responsibilities<\/h4>\n<ul>\n<li>It sets out the requirements for security information.<\/li>\n<li>It has the ultimate responsibility for the use of critical information and therefore for its protection.<\/li>\n<li>It shall determine the security levels in each dimension of the information.<\/li>\n<li>Although the formal approval of the levels of information depends on the Information Manager, the Information Manager may seek a proposal from the Information Security Officer, the ISMS Manager and the System Security Administration, the latter if applicable.<\/li>\n<\/ul>\n<h4><a name=\"_Toc44501022\"><\/a>Compatibility with other Roles<\/h4>\n<p>This role may coincide with that of the Service Manager.<\/p>\n<p>This role shall not coincide with that of Information Security Officer, ISMS Manager or System Security Administrator, the latter if applicable.<\/p>\n<h4><a name=\"_Toc519697778\"><\/a>6.1.2 <u>Service Manager<\/u><\/h4>\n<p>Where different from the Information Manager, it may be at the level of a top-level governing body, like the Information Manager, or it may be at the level of an executive directorate or management, which understands what each department does and how departments coordinate with each other to achieve the objectives set by the relevant higher bodies.<\/p>\n<p>Their functions may be assigned to a natural person or by the Information Security Committee.<\/p>\n<p>The person or body that undertakes it shall be identified for each Service provided by the organisation.<\/p>\n<h4>Associated Functions and Responsibilities<\/h4>\n<ul>\n<li>Establishes the security requirements for services.<\/li>\n<li>It has the ultimate responsibility for the use of certain services and therefore for their protection. In case of the existence of a Service Provider, it shall be responsible for managing and mitigating errors or negligent actions under its control that may lead to service availability incidents.<\/li>\n<li>It shall determine the security levels in each dimension of the service.<\/li>\n<li>Although the formal approval of the levels depends on the Service Manager, the Service Manager may seek a proposal from the Information Security Officer, the ISMS Manager and the System Security Administrator, the latter if applicable.<\/li>\n<li>The provision of a service always has to meet the security requirements of the information it handles, as well as the security requirements of the service, adding availability requirements and others, such as accessibility and interoperability.<\/li>\n<\/ul>\n<h4><a name=\"_Toc44501025\"><\/a>Compatibility with other Roles<\/h4>\n<p>This role may coincide with that of the Information Manager.<\/p>\n<p>This role shall not coincide with that of Information Security Officer, ISMS Manager or System Security Administrator, the latter if applicable.<\/p>\n<h4><a name=\"_Toc44501026\"><\/a><a name=\"_Toc1777428219\"><\/a>6.1.3 <u>Information Security Officer \/ CISO<\/u><\/h4>\n<p>It corresponds to the level of an Executive Directorate or Management.<\/p>\n<p>Only one person in the organisation shall be formally appointed as the Information Security Officer, although the Information Security Officer may delegate part of the functions to other people called delegates.<\/p>\n<h4><a name=\"_Toc44501027\"><\/a>Associated Functions and Responsibilities<\/h4>\n<ul>\n<li>Shall report directly to the Information Security Committee.<\/li>\n<li>Shall act as Secretary of the Information Security Committee.<\/li>\n<li>Convene the Information Security Committee.<\/li>\n<li>Maintain the security of the information used, the services provided and the information systems.<\/li>\n<li>Promote information security training and awareness.<\/li>\n<li>It shall compile the security requirements of the Information and Service Officers together with the ISMS Manager and determine the criticality of the system.<\/li>\n<li>Conduct the Risk Analysis.<\/li>\n<li>Produce a Statement of Applicability based on the required security measures according to the ISO 27001 and NIS2, and the result of the Risk Analysis.<\/li>\n<li>Provide management and other Committee members with information on the level of residual risk expected after implementing the processing options selected in the risk analysis and the required security measures.<\/li>\n<li>Shall coordinate the preparation of the System Security Documentation.<\/li>\n<li>Shall participate in the elaboration, within the framework of the Information Security Committee, of the Information Security Policy, for approval by the management.<\/li>\n<li>Shall participate in the drafting and approval of the organisation\u2019s information security policies, procedures and internal regulations within the framework of the Information Security Committee<\/li>\n<li>Develop, maintain and approve operational information security procedures.<\/li>\n<li>Shall regularly provide the Security Committee with a summary of security actions, information security incidents and the security status of the system.<\/li>\n<li>Shall elaborate, together with the ISMS Manager, Security Improvement Plans for approval by the Information Security Committee.<\/li>\n<li>Shall promote training and awareness as well as elaborate Information Security Training and Awareness Plans for personnel, which shall be approved by the Information Security Committee.<\/li>\n<li>Shall validate the Systems Continuity Plans elaborated by the ISMS Manager, which shall be approved by the Information Security Committee and periodically tested by the ISMS Manager.<\/li>\n<li>Approve the guidelines proposed by the ISMS Manager to consider Information Security throughout the lifecycle of assets and processes: specification, architecture, development, operation and changes.<\/li>\n<\/ul>\n<h4>In the event of an information security incident<\/h4>\n<h4>The Information Security Officer shall analyse and propose safeguards to prevent similar incidents in the future.<\/h4>\n<h4><a name=\"_Toc44501028\"><\/a>Compatibility with other roles<\/h4>\n<p>This role may not coincide with that of ISMS Manager and System Security Administrator, the latter if applicable.<\/p>\n<h4>Delegation of Functions<\/h4>\n<p>For certain Information Systems which, due to their complexity, distribution, physical separation of their elements or number of users, require additional personnel to carry out the functions of the Information Security Officer, the Delegated Security Officers deemed necessary may be appointed by the Information Security Officer, prior approval by the Information Security Committee.<\/p>\n<p>Through the designation of delegates, functions are delegated. The ultimate responsibility remains with the Information Security Officer.<\/p>\n<p>The Delegated Security Officers shall be in charge of all the functions delegated by the Information Security Officer and shall report directly to the Information Security Officer.<\/p>\n<h4><a name=\"_Toc2109183911\"><\/a>6.1.4 <u>ISMS Manager<\/u><\/h4>\n<p>Corresponds to the level of an Operational Directorate.<\/p>\n<p>A natural person shall be formally appointed as ISMS Manager.<\/p>\n<h4>Associated Functions and Responsibilities<\/h4>\n<p>Its functions shall be as follows:<\/p>\n<ul>\n<li>Establish, review and maintain the organisation&#8217;s information security policy.<\/li>\n<li>Coordinate the identification, analysis and treatment of risks.<\/li>\n<li>Ensure the application of security controls and measures.<\/li>\n<li>Coordinate internal ISMS audits and the resulting corrective actions.<\/li>\n<li>Manage ISMS documentation, including the Statement of Applicability (SoA), in collaboration with the Information Security Officer.<\/li>\n<li>Collaborate with the Information Security Officer, the DPO and other key roles to ensure the integration of security and privacy across the organisation.<\/li>\n<\/ul>\n<h4><a name=\"_Toc44501032\"><\/a>In the event of an information security incident<\/h4>\n<h4>Shall plan the implementation of safeguards in the system and shall implement the approved security plan.<\/h4>\n<h4>Compatibility with other Roles<\/h4>\n<p>This role shall not coincide with that of the System Security Administrator and Information Security Officer.<\/p>\n<h4><a name=\"_Toc44501034\"><\/a><a name=\"_Toc2078199970\"><\/a>6.1.5 <u>System Security Administrator<\/u><\/h4>\n<p>Corresponds to the level of a qualified employee in IT systems security.<\/p>\n<p>The System Security Administrator shall be nominated by the ISMS Manager, to whom the System Security Administrator shall report on all matters relating to information security of the systems managed.<\/p>\n<h4>Associated Functions and Responsibilities<\/h4>\n<ul>\n<li>The implementation, management and maintenance of the security measures applicable to the Information System.<\/li>\n<li>Ensure that established security controls are strictly implemented.<\/li>\n<li>Ensure that audit trails and required security logs are enabled, retained and monitored in accordance with the organisation\u2019s information security requirements.<\/li>\n<li>Implement, operate and maintain the required security procedures, mechanisms and controls for systems, users and associated internal and external assets.<\/li>\n<li>Ensure that the approved procedures for managing the information system and the required security mechanisms and services are applied.<\/li>\n<li>The management, configuration and updating, where appropriate, of the hardware and software on which the security mechanisms and services of the Information System are based.<\/li>\n<li>Monitor hardware and software installations, modifications and upgrades to ensure that security is not compromised.<\/li>\n<li>Approve changes to the current configuration of the Information System, ensuring that the security mechanisms and services in place remain operational.<\/li>\n<li>Report any security-related anomalies, compromises or vulnerabilities to the ISMS Manager.<\/li>\n<li>Monitor the security status of the system.<\/li>\n<\/ul>\n<h4><a name=\"_Toc44501036\"><\/a>In the event of an information security incident<\/h4>\n<ul>\n<li>Logging, accounting and management of security incidents in the systems under his responsibility.<\/li>\n<li>Implement the approved security plan.<\/li>\n<li>Isolate the incident to prevent spread to other elements not compromised by the incident.<\/li>\n<li>Take short-term decisions if information has been compromised in a way that could have serious consequences (these actions shall be documented).<\/li>\n<li>Ensure the integrity of critical elements of the System if their availability has been affected.<\/li>\n<li>Maintain and retrieve the information stored by the System and its associated services.<\/li>\n<li>Investigate the incident: determine the characteristics, means, motives and origin of the incident.<\/li>\n<\/ul>\n<h4>Compatibility with other roles<\/h4>\n<p>This role shall not coincide with the role of ISMS Manager and Information Security Officer.<\/p>\n<h4><a name=\"_Toc44501038\"><\/a>Delegation of Functions<\/h4>\n<p>For certain Information Systems which, due to their complexity, distribution, physical separation of their elements or number of users, require additional personnel to carry out the functions of the System Security Administrator, the Delegated System Security Administrators deemed necessary may be appointed by the System Security Administrator, prior approval by the Information Security Committee.<\/p>\n<p>Through the designation of delegates, functions are delegated. The ultimate responsibility remains with the Security System Administrator.<\/p>\n<p>The Delegated Security Systems Administrators shall be in charge of all the functions delegated by the Security System Administrator and shall report directly to the Security System Administrator.<\/p>\n<h4><a name=\"_Toc90979987\"><\/a><a name=\"_Toc1185591366\"><\/a>6.1.6 <u>Data Protection Officer<\/u><\/h4>\n<p>The Data Protection Officer is a role contemplated by the RGPD (European Data Protection Regulation) and the applicable Spanish Organic Law 3\/2018 on General Protection of Personal Data.<\/p>\n<p>Such role shall be assumed by a natural person.<\/p>\n<h4>Associated Functions and Responsibilities<\/h4>\n<ul>\n<li>Reporting directly to the highest hierarchical level recommendations, assessments or advice regarding personal data protection.<\/li>\n<li>Collaborate with the Information Security Officer in the event of security incidents which may affect personal data.<\/li>\n<li>Supervise compliance of applicable privacy law, both internally and externally regarding providers.<\/li>\n<li>Assist on the assessment of risks related to personal data and safeguards thereof.<\/li>\n<li>Participate in awareness and training activities related to data protection matters.<\/li>\n<\/ul>\n<h3><a name=\"_Toc44501039\"><\/a><a name=\"_Toc1215727113\"><\/a><a name=\"_Toc102129582\"><\/a><a name=\"_Toc102129774\"><\/a><a name=\"_Toc102130880\"><\/a><a name=\"_Toc102132421\"><\/a><a name=\"_Toc102129583\"><\/a><a name=\"_Toc102129775\"><\/a><a name=\"_Toc102130881\"><\/a><a name=\"_Toc102132422\"><\/a><a name=\"_Toc102129584\"><\/a><a name=\"_Toc102129776\"><\/a><a name=\"_Toc102130882\"><\/a><a name=\"_Toc102132423\"><\/a><a name=\"_Toc102129585\"><\/a><a name=\"_Toc102129777\"><\/a><a name=\"_Toc102130883\"><\/a><a name=\"_Toc102132424\"><\/a><a name=\"_Toc102129586\"><\/a><a name=\"_Toc102129778\"><\/a><a name=\"_Toc102130884\"><\/a><a name=\"_Toc102132425\"><\/a><a name=\"_Toc102129587\"><\/a><a name=\"_Toc102129779\"><\/a><a name=\"_Toc102130885\"><\/a><a name=\"_Toc102132426\"><\/a><a name=\"_Toc102129588\"><\/a><a name=\"_Toc102129780\"><\/a><a name=\"_Toc102130886\"><\/a><a name=\"_Toc102132427\"><\/a><a name=\"_Toc102129589\"><\/a><a name=\"_Toc102129781\"><\/a><a name=\"_Toc102130887\"><\/a><a name=\"_Toc102132428\"><\/a><a name=\"_Toc102129590\"><\/a><a name=\"_Toc102129782\"><\/a><a name=\"_Toc102130888\"><\/a><a name=\"_Toc102132429\"><\/a><a name=\"_Toc102129591\"><\/a><a name=\"_Toc102129783\"><\/a><a name=\"_Toc102130889\"><\/a><a name=\"_Toc102132430\"><\/a><a name=\"_Toc102129592\"><\/a><a name=\"_Toc102129784\"><\/a><a name=\"_Toc102130890\"><\/a><a name=\"_Toc102132431\"><\/a><a name=\"_Toc102129593\"><\/a><a name=\"_Toc102129785\"><\/a><a name=\"_Toc102130891\"><\/a><a name=\"_Toc102132432\"><\/a><a name=\"_Toc102129594\"><\/a><a name=\"_Toc102129786\"><\/a><a name=\"_Toc102130892\"><\/a><a name=\"_Toc102132433\"><\/a><a name=\"_Toc102129595\"><\/a><a name=\"_Toc102129787\"><\/a><a name=\"_Toc102130893\"><\/a><a name=\"_Toc102132434\"><\/a><a name=\"_Toc102129596\"><\/a><a name=\"_Toc102129788\"><\/a><a name=\"_Toc102130894\"><\/a><a name=\"_Toc102132435\"><\/a><a name=\"_Toc102129597\"><\/a><a name=\"_Toc102129789\"><\/a><a name=\"_Toc102130895\"><\/a><a name=\"_Toc102132436\"><\/a><a name=\"_Toc63239138\"><\/a>6.2 Responsibilities under ISO 27001 and NIS 2<\/h3>\n<p>The main responsibilities are shown below in correlation with the security measures:<\/p>\n<p>In this regard, see the following document: \u201cREG-03 RACI\u201d.<\/p>\n<h2><a name=\"_Toc2013708741\"><\/a>7. Personal Data<\/h2>\n<p>KYMOS processes personal data, thus, the organisation has the corresponding <strong><em>Register of Processing Activities <\/em><\/strong>according to the RGPD dispositions.<\/p>\n<p>All KYMOS Group information systems shall comply with the security levels required by the regulations, for the purpose and effect of the nature and purpose of the personal data collected.<\/p>\n<h2><a name=\"_Toc44501040\"><\/a><a name=\"_Toc1413773657\"><\/a>8. Risk Management<\/h2>\n<h3><a name=\"_Toc44501041\"><\/a><a name=\"_Toc2021161286\"><\/a>8.1 Justification<\/h3>\n<p>All systems subject to this Policy will be required to perform a risk analysis, assessing the threats and risks to which they are exposed.<\/p>\n<p>The risk analysis will be the basis for determining the security measures to be taken which shall be detailed in the Risk Analysis and its Statement of Applicability.<\/p>\n<h3><a name=\"_Toc44501042\"><\/a><a name=\"_Toc808411736\"><\/a>8.2 Risk assessment criteria<\/h3>\n<p>For the harmonisation of risk analysis methodology, the Information Security Committee shall establish a baseline assessment for the different types of information handled and the different services provided.<\/p>\n<p>Detailed risk assessment criteria shall be specified in the risk assessment methodology to be developed by the organisation, based on recognised standards and practices.<\/p>\n<p>All risks that could seriously prevent the operational capability of the organisation or the achievement of the organisation&#8217;s mission shall be addressed.<\/p>\n<p>Special priority shall be given to risks involving an interruption of the provision of services rendered.<\/p>\n<h3><a name=\"_Toc44501043\"><\/a><a name=\"_Toc1338927843\"><\/a>8.3 Treatment guidelines<\/h3>\n<p>The Information Security Committee will streamline the availability of resources to meet the security needs of the different systems, promoting horizontal investments.<\/p>\n<h3><a name=\"_Toc44501044\"><\/a><a name=\"_Toc1483219785\"><\/a>8.4 Residual Risk Acceptance Process<\/h3>\n<p>Residual risks shall be determined by the Information Security Officer.<\/p>\n<p>The residual Risk levels expected on each Information after the implementation of the treatment options (including the implementation of the security measures foreseen in ISO 27002 and in the NIS2 Directive) shall be accepted by the Information Security Committee.<\/p>\n<p>The Residual Risk levels shall be submitted by the Information Security Officer to the Information Security Committee (ISC), which shall evaluate, approve or rectify the proposed treatment options as appropriate.<\/p>\n<h3><a name=\"_Toc44501045\"><\/a><a name=\"_Toc1814599292\"><\/a>8.5 Need to conduct or update risk assessments<\/h3>\n<p>The analysis of risks and their treatment must be a regular activity, as required by ISO 27001 and the NIS2 Directive. This analysis shall be repeated:<\/p>\n<ul>\n<li>Regularly, at least once a year.<\/li>\n<li>When there are significant changes in the information handled.<\/li>\n<li>When there are significant changes in the services provided.<\/li>\n<li>When significant changes occur in the systems that process information and are involved in the provision of services.<\/li>\n<li>When a serious security incident occurs.<\/li>\n<li>When serious vulnerabilities are reported.<\/li>\n<\/ul>\n<h2><a name=\"_Toc44501046\"><\/a><a name=\"_Toc1320272264\"><\/a>9. Obligations of Staff<\/h2>\n<p>All members of the organisation are obliged to know and comply with this Information Security Policy and the Security Regulations applicable to them, and it is the responsibility of the Information Security Committee to provide the necessary means to ensure that the information reaches those affected.<\/p>\n<p>Compliance with this Security Policy is mandatory for all internal and external personnel involved in the organisation&#8217;s processes, and non-compliance with it constitutes a serious offence for employment purposes, in accordance with the collective labour agreement.<\/p>\n<p>In this regard, the organisation has the document \u201cIT-REGU-04 Security Regulations of Duties and Roles of Staff\u201d.<\/p>\n<h2><a name=\"_Toc1076253123\"><\/a>10. Staff Training and Awareness<\/h2>\n<p>The Management is committed to the Professional Training and Awareness of KYMOS Group Staff.<\/p>\n<p>KYMOS\u2019s objective is to continuously raise awareness of cybersecurity among employees, and to this end, the organisation carries out:<\/p>\n<ul>\n<li>Timely delivery of information pills on cybersecurity, responding to risk situations.<\/li>\n<li>Annual Cybersecurity refresher training for all staff.<\/li>\n<li>Sporadic phishing simulation campaigns, at least every two years.<\/li>\n<\/ul>\n<h2><a name=\"_Toc44501047\"><\/a><a name=\"_Toc1991650088\"><\/a>11. Third Parties<\/h2>\n<p>When services are provided or information is managed by other organisations, they shall be made aware of this Information Security Policy, reporting and coordination channels shall be established for the respective Information Security Committees, and procedures shall be established for reacting to security incidents.<\/p>\n<p>Where third party services are used or information is provided to third parties, they will be made aware of this Security Policy and the Roles and Duties of the Staff that applies to these services or information. This third party shall be subject to the obligations set out in this policy and may develop its own operating procedures to meet these obligations.<\/p>\n<p>Specific incident reporting and resolution procedures shall be established. It shall be ensured that third party personnel are adequately security-aware to at least the same level as set out in this Policy.<\/p>\n<p>Where any aspect of the Policy cannot be satisfied by a third party as required in the above paragraphs, a report from the Information Security Officer specifying the risks involved and how they will be addressed will be required. Such report shall be reviewed by the Information Security Committee and approved by the Information and Service Managers, together with the Management.<\/p>\n<h2><a name=\"_Toc44501048\"><\/a><a name=\"_Toc1503528997\"><\/a>12. Review and Approval of the Security Policy<\/h2>\n<p>The Information Security Policy shall be reviewed by the Information Security Committee at planned intervals, not exceeding one year, or whenever significant changes occur in order to ensure that its suitability, adequacy and effectiveness are maintained.<\/p>\n<p>Any changes to the Information Security Policy shall be reviews by the Information Security Committee and approved by Management.<\/p>\n<p>Management shall ensure that all personnel understand and fulfil their information security responsibilities as well as shall promote compliance with information security policies, procedures and controls and shall provide the necessary support and resources for their implementation.<\/p>\n<p>Finally, the Information Security Policy shall be communicated and made available to all KYMOS Group personnel and stakeholders.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":8,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"100-width.php","meta":{"_acf_changed":false,"footnotes":""},"categories":[],"tags":[],"class_list":["post-40063","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Information Security Policy | Kymos<\/title>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"ko_KR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Information Security Policy | Kymos\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kymos.com\/ko\/information-security-policy\/\" \/>\n<meta property=\"og:site_name\" content=\"Kymos\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-10T13:08:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kymos.com\/wp-content\/uploads\/2023\/06\/Foto-Logo-Kymos-Edificio.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"1200\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@KymosGroup\" \/>\n<meta name=\"twitter:label1\" content=\"\uc608\uc0c1 \ub418\ub294 \ud310\ub3c5 \uc2dc\uac04\" \/>\n\t<meta name=\"twitter:data1\" content=\"24\ubd84\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kymos.com\\\/ko\\\/information-security-policy\\\/\",\"url\":\"https:\\\/\\\/kymos.com\\\/ko\\\/information-security-policy\\\/\",\"name\":\"Information Security Policy | Kymos\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kymos.com\\\/ko\\\/#website\"},\"datePublished\":\"2026-06-10T12:53:30+00:00\",\"dateModified\":\"2026-06-10T13:08:53+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kymos.com\\\/ko\\\/information-security-policy\\\/#breadcrumb\"},\"inLanguage\":\"ko-KR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kymos.com\\\/ko\\\/information-security-policy\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kymos.com\\\/ko\\\/information-security-policy\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kymos.com\\\/ko\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Information Security Policy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kymos.com\\\/ko\\\/#website\",\"url\":\"https:\\\/\\\/kymos.com\\\/ko\\\/\",\"name\":\"Kymos Group\",\"description\":\"Kymos Group\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kymos.com\\\/ko\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ko-KR\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Information Security Policy | Kymos","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"ko_KR","og_type":"article","og_title":"Information Security Policy | Kymos","og_url":"https:\/\/kymos.com\/ko\/information-security-policy\/","og_site_name":"Kymos","article_modified_time":"2026-06-10T13:08:53+00:00","og_image":[{"width":1200,"height":1200,"url":"https:\/\/kymos.com\/wp-content\/uploads\/2023\/06\/Foto-Logo-Kymos-Edificio.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_site":"@KymosGroup","twitter_misc":{"\uc608\uc0c1 \ub418\ub294 \ud310\ub3c5 \uc2dc\uac04":"24\ubd84"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/kymos.com\/ko\/information-security-policy\/","url":"https:\/\/kymos.com\/ko\/information-security-policy\/","name":"Information Security Policy | Kymos","isPartOf":{"@id":"https:\/\/kymos.com\/ko\/#website"},"datePublished":"2026-06-10T12:53:30+00:00","dateModified":"2026-06-10T13:08:53+00:00","breadcrumb":{"@id":"https:\/\/kymos.com\/ko\/information-security-policy\/#breadcrumb"},"inLanguage":"ko-KR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kymos.com\/ko\/information-security-policy\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/kymos.com\/ko\/information-security-policy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kymos.com\/ko\/"},{"@type":"ListItem","position":2,"name":"Information Security Policy"}]},{"@type":"WebSite","@id":"https:\/\/kymos.com\/ko\/#website","url":"https:\/\/kymos.com\/ko\/","name":"Kymos Group","description":"Kymos Group","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kymos.com\/ko\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ko-KR"}]}},"_links":{"self":[{"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/pages\/40063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/comments?post=40063"}],"version-history":[{"count":3,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/pages\/40063\/revisions"}],"predecessor-version":[{"id":40087,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/pages\/40063\/revisions\/40087"}],"wp:attachment":[{"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/media?parent=40063"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/categories?post=40063"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kymos.com\/ko\/wp-json\/wp\/v2\/tags?post=40063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}