Information Security Policy
KOGNIA · SGSI-PO-001
Version 2 · Approval: November 10, 2026
Classification: public documentation
- Introduction
- Purpose
- Scope and applicability
- Framework for information security objectives
- Information security principles
- Top Management commitment
- General roles and responsibilities
- Management of risks and opportunities
- Protection of information and associated assets
- Access control
- Acceptable use of information and associated assets
- Security by design, development, and artificial intelligence
- Supplier and third-party management
- Event and incident reporting and management
- Continuity and resilience
- Competence, awareness, and communication
- Compliance, exceptions, and noncompliance
- Monitoring, review, and improvement
- Approval and effective period
1. Introduction
KOGNIA is a technology company specializing in the design, development, implementation, deployment, operation, support, and maintenance of artificial intelligence-based enterprise solutions. Its services combine generative artificial intelligence, automation, and enterprise integration through cognitive agents capable of understanding, reasoning, and taking action.
Due to the nature of its services, KOGNIA's operations depend on the secure handling of information and the protection of the assets used to deliver its services. Information security and the responsible use of technology and artificial intelligence are essential to protecting KOGNIA and its customers, supporting operational continuity, and meeting applicable requirements.
This Corporate Information Security Policy establishes the principles, commitments, and general guidelines adopted by KOGNIA to protect the confidentiality, integrity, and availability of information and other associated assets. It also incorporates corporate Acceptable Use guidelines applicable to individuals who use information, systems, devices, technology services, and other assets under KOGNIA's responsibility.
The guidelines incorporated to complete the Acceptable Use framework reflect generally recommended information security practices. Once this policy is approved, they will become part of KOGNIA's internal obligations and must be developed through any necessary standards, procedures, and work instructions.
2. Purpose
The purpose of this policy is to:
- establish the corporate framework for directing information security;
- support the establishment and review of information security objectives;
- define general commitments to manage risks and protect information and associated assets;
- establish Acceptable Use rules for information and technology assets;
- assign general compliance responsibilities; and
- express KOGNIA's commitment to meeting applicable requirements and continually improving its Information Security Management System, hereinafter referred to as the ISMS.
3. Scope and applicability
This policy applies to:
- members of Top Management;
- all employees and other personnel;
- contractors, suppliers, partners, and authorized third parties; and
- any person who accesses, uses, manages, stores, processes, or transmits information or technology assets belonging to KOGNIA or its customers under KOGNIA's responsibility.
It covers information in any format or medium, including verbal, printed, digital, audiovisual, or otherwise recorded information; the systems, networks, facilities, devices, and services used to store, process, or transmit it; and information entrusted to KOGNIA by customers or other parties.
It also applies to activities carried out using KOGNIA's assets or involving access to information under its responsibility, regardless of whether they are performed remotely, from third-party locations, or through externally provided infrastructure and services.
Compliance is mandatory for the processes, services, technologies, working arrangements, and activities included within the current scope of the ISMS.
The detailed scope of the ISMS is documented in section 2.2 of SGSI-MN-003 ISMS Management Manual. This policy does not, by itself, extend the formal boundaries of that scope, although its Acceptable Use rules may be enforced for any person whom KOGNIA authorizes to access its assets or information.
4. Framework for information security objectives
KOGNIA will establish information security objectives at relevant functions and levels. These objectives must be consistent with this policy, consider applicable requirements and the results of risk assessment and treatment, be measurable where practicable, have defined responsibilities and resources, and be monitored, communicated, and updated.
Information security objectives will focus on:
- protecting the confidentiality, integrity, and availability of information;
- managing information security risks in accordance with approved criteria;
- maintaining controls proportionate to business needs and identified risks;
- preventing, detecting, reporting, and addressing information security events and incidents;
- strengthening individuals' competence, awareness, and secure behavior;
- meeting legal, regulatory, contractual, and organizational requirements determined to be applicable;
- evaluating the performance and effectiveness of the ISMS; and
- continually improving the suitability, adequacy, and effectiveness of the ISMS.
Objectives will be planned, approved, monitored, updated, and closed in accordance with SGSI-PR-001 Strategic Processes and the current objectives program.
5. Information security principles
KOGNIA will manage information security according to the following principles:
5.1 Confidentiality
Information will be accessible only to authorized individuals, processes, or entities and in accordance with a legitimate need.
5.2 Integrity
Information and associated assets will be protected against unauthorized, accidental, or improper modification, destruction, or alteration.
5.3 Availability
Information, systems, and services will be available to authorized individuals in accordance with applicable needs and commitments.
5.4 Risk-based management
Security decisions will be based on risk assessment and treatment and on business needs. The measures adopted must be proportionate to the level of risk and applicable requirements.
5.5 Least privilege and need to know
Access to information and other associated assets will be limited to what is necessary to perform authorized functions.
5.6 Individual and shared responsibility
Each individual is responsible for protecting the information and assets they use. Those responsible for processes, services, and assets must implement and oversee security requirements within their areas of responsibility.
5.7 Security by design
Information security requirements will be considered from the relevant stages of the design, acquisition, development, implementation, modification, and retirement of processes, products, services, and technologies.
5.8 Compliance and traceability
Relevant security activities must be carried out in accordance with approved rules and generate the documented information necessary to demonstrate their completion and results.
5.9 Continual improvement
KOGNIA will continually evaluate and improve the suitability, adequacy, and effectiveness of the ISMS.
6. Top Management commitment
Top Management is committed to:
- ensuring that this policy and the information security objectives are compatible with KOGNIA's strategic direction;
- integrating ISMS requirements into the organization's relevant processes;
- providing the resources needed to establish, implement, maintain, and improve the ISMS;
- communicating the importance of effective information security management and compliance with ISMS requirements;
- ensuring that the ISMS achieves its intended outcomes;
- directing and supporting individuals so that they contribute to the effectiveness of the ISMS;
- supporting relevant management roles in fulfilling their security responsibilities;
- promoting a culture of information security;
- meeting applicable information security requirements;
- continually improving the ISMS.
7. General roles and responsibilities
Detailed ISMS responsibilities and authorities must be maintained in SGSI-MN-004 Roles and Responsibilities or an equivalent organizational record. At a minimum, the following general responsibilities will apply:
7.1 Top Management
Top Management will approve this policy and its amendments, establish or approve objectives, allocate relevant resources, promote compliance, conduct management reviews, and make the necessary decisions regarding the ISMS.
7.2 ISMS Manager
The ISMS Manager will coordinate the establishment, implementation, maintenance, monitoring, and improvement of the ISMS; facilitate the implementation of this policy; report to Top Management on the system's performance; and coordinate the retention of relevant documented information.
The named appointment and the relationship between the ISMS Manager and the AI Security & Technology Operations Manager role must remain formally documented.
7.3 Those responsible for processes, services, and assets
Those responsible for processes, services, and assets must:
- apply the relevant requirements and controls within their areas;
- ensure that individuals under their coordination understand their responsibilities;
- identify and communicate risks, changes, incidents, deviations, and improvement needs;
- provide the resources and evidence for which they are responsible; and
- verify completion of assigned actions.
7.4 Authorized users and third parties
Every person subject to this policy must:
- understand and comply with the security requirements applicable to their functions;
- use information and assets only for authorized purposes;
- protect the credentials, devices, information, and resources assigned to them;
- participate in the awareness and training activities applicable to them;
- promptly report known or suspected events, incidents, vulnerabilities, losses, or instances of noncompliance; and
- return assets and continue to fulfill any obligations that remain in effect when their relationship with KOGNIA changes or ends.
8. Management of risks and opportunities
KOGNIA will identify, analyze, evaluate, treat, monitor, and review information security risks that may affect its objectives, processes, services, information, or associated assets.
Assessments must consider the potential loss of confidentiality, integrity, or availability, identify risk owners, and use approved criteria that produce consistent, valid, and comparable results.
Treatment options, necessary controls, the Risk Treatment Plan, the Statement of Applicability, and acceptance of residual risks must be documented and approved by the appropriate authorities.
General risks and opportunities that may affect the ISMS's ability to achieve its intended outcomes will be managed in accordance with SGSI-PR-001 Strategic Processes. Formal information security risk assessment and treatment will be governed by the specific methodology approved by KOGNIA.
9. Protection of information and associated assets
Information and other associated assets must be identified, managed, and protected throughout their lifecycle according to their importance, classification, risks, and applicable requirements.
KOGNIA will establish the rules necessary to:
- maintain inventories and responsibilities for relevant assets;
- classify and, where appropriate, label information;
- control the access, use, storage, reproduction, transmission, retention, and deletion of information;
- protect information stored, processed, or accessible through user devices;
- manage storage media securely;
- return, retire, or dispose of assets when they are no longer needed or when authorization to use them ends; and
- preserve the records required as evidence of ISMS activities.
Employment, contractual, or service provision terms must incorporate the information security responsibilities appropriate to the role and authorized access. Where necessary, confidentiality or nondisclosure commitments must be formalized before access to protected information is allowed.
Confidentiality, intellectual property, and information protection obligations will continue after a change or termination of an employment, contractual, or commercial relationship where required by applicable agreements or requirements.
10. Access control
Physical and logical access to information and other associated assets must be authorized and managed based on business needs, information security, least privilege, need to know, and segregation of duties where appropriate.
KOGNIA must manage the lifecycle of identities and access rights, including their creation, approval, provisioning, review, modification, suspension, and removal.
Accounts and elevated privileges must be assigned in a restricted and controlled manner. Users must protect authentication information and use the authentication mechanisms established by KOGNIA.
The following are prohibited:
- sharing passwords, codes, tokens, certificates, keys, or other means of authentication;
- using another person's credentials or allowing another person to use one's own;
- attempting to access information, systems, functions, or spaces without authorization;
- bypassing, weakening, disabling, or altering access controls or authentication mechanisms without authorization; and
- retaining access that is no longer necessary for assigned functions.
11. Acceptable use of information and associated assets
KOGNIA will establish, document, communicate, and implement rules for the acceptable use and secure handling of information and other associated assets.
All authorized individuals must use information, systems, devices, and technology services only for legitimate and authorized purposes, in accordance with their functions, applicable requirements, and the protection measures established by KOGNIA.
The detailed rules applicable to employees, contractors, suppliers, and other authorized third parties are set out in SGSI-PO-005 Acceptable Use Policy, an internal document that supplements this policy.
12. Security by design, development, and artificial intelligence
KOGNIA will incorporate security and risk management requirements into the relevant stages of the design, acquisition, development, testing, implementation, deployment, operation, maintenance, and retirement of solutions and services.
Security requirements must be identified, documented, and reviewed with the relevant functions from the early stages of projects and significant changes. Depending on the nature and risk of the initiative, their determination may consider applicable obligations, threat modeling, lessons learned from incidents, authentication and authorization needs, asset protection, logging and monitoring, information leakage prevention, and security acceptance criteria.
Development, testing, and production environments and access must be managed according to the identified risks and responsibilities. Access to source code, development tools, artifacts, models, data, configurations, and secrets must be restricted and protected.
Artificial intelligence-based solutions must consider information protection, access control, traceability, protection of data and artifacts, validation of results, oversight, and applicable requirements, according to their purpose and risk.
13. Supplier and third-party management
KOGNIA will manage information security risks associated with products and services supplied by third parties.
Suppliers, contractors, partners, and third parties that access information or assets must comply with the security and confidentiality requirements applicable to them. These requirements must be established in relevant agreements, contracts, terms, or mechanisms according to the nature of the relationship and the risk.
Relevant third-party services must be subject to monitoring, review, and change management in accordance with the responsibilities of KOGNIA and the supplier and the applicable shared responsibility model.
14. Event and incident reporting and management
Every person subject to this policy must report known or suspected security events and incidents without delay through the channels established by KOGNIA.
The following, among others, must be reported:
- loss, theft, or compromise of devices, credentials, or information;
- unauthorized access, disclosure, modification, deletion, or use;
- suspicious messages, links, files, or requests;
- malicious code or abnormal system behavior;
- observed vulnerabilities or security weaknesses;
- noncompliance with this policy or other security requirements; and
- incidents associated with suppliers, cloud services, or artificial intelligence tools.
KOGNIA will establish and communicate processes, roles, and responsibilities to assess, respond to, document, and learn from events and incidents, preserve evidence where appropriate, and reduce the likelihood or impact of recurrence.
15. Continuity and resilience
KOGNIA will determine the information security requirements that must be maintained during adverse situations or disruptions and establish continuity and recovery measures appropriate to business needs, risks, and applicable commitments.
Continuity, backup, recovery, and redundancy mechanisms must be planned, maintained, and tested in accordance with the requirements established in the applicable operational documents.
16. Competence, awareness, and communication
KOGNIA will determine the necessary competence of individuals whose activities may affect information security performance and retain appropriate evidence of education, training, or experience.
Before granting access, KOGNIA will communicate the security responsibilities and rules relevant to each individual's role. Awareness and training will be updated throughout the relationship when required by risks, responsibilities, relevant changes, or monitoring results.
Individuals under KOGNIA's control must be aware of:
- this policy and the topic-specific guidelines relevant to their functions;
- their contribution to the effectiveness of the ISMS;
- their protection and Acceptable Use responsibilities; and
- the consequences of failing to comply with ISMS requirements.
KOGNIA will communicate this policy within the organization and make it available to relevant interested parties where appropriate.
17. Compliance, exceptions, and noncompliance
All individuals covered by this policy must comply with its provisions and other applicable ISMS documents.
Exceptions must:
- address a legitimate and documented need;
- be supported by a risk assessment;
- identify the scope, owner, duration, and compensating measures;
- be approved by the designated authority;
- be reviewed and withdrawn when their justification no longer applies.
Noncompliance may result in administrative, disciplinary, contractual, or legal measures, as appropriate to the relationship with KOGNIA and applicable requirements. Such measures must be managed through formally established processes and comply with applicable legislation and agreements.
18. Monitoring, review, and improvement
KOGNIA will monitor, measure, analyze, and evaluate information security performance and the effectiveness of the ISMS. Relevant results will be used for decision-making, management review, and the identification of corrections and opportunities for improvement.
This policy will be reviewed at least annually and whenever significant changes occur that may affect its suitability or adequacy, including changes to the ISMS, the business, risks, services, technologies, or applicable requirements.
Amendments must be reviewed and approved in accordance with SGSI-MN-001 ISMS Document Control. Document review does not replace the evaluation of the implementation or effectiveness of associated controls.
KOGNIA will continually improve the suitability, adequacy, and effectiveness of the ISMS through risk treatment, monitoring of objectives and indicators, audits, management review, incident management, corrective actions, and opportunities for improvement.
19. Approval and effective period
This policy will take effect upon approval by Top Management and will remain in effect until it is replaced or withdrawn through the document control process.
Approval of this policy endorses its content only. Approval of objectives, procedures, matrices, plans, and other ISMS documents must be recorded in each document or record in accordance with the applicable document control authorities and rules.