Technical and Organisational Security Measures
Version 1.1 — June 2026
Structure and regulatory references
This document describes the technical and organisational security measures adopted by AtWorkStudio S.r.l. in the provision of its services. It is organised according to the controls of ISO/IEC 27001:2022 (Annex A, 93 controls grouped into four themes: organisational, people, physical and technological), integrated with the cloud service-specific controls of Annex A of ISO/IEC 27017:2015 and with the additional controls for the processing of personally identifiable information in the cloud of ISO/IEC 27018:2025. The document also takes into account the risk related to climate change as required by Amendment A1:2024 of ISO/IEC 27001.
AtWorkStudio is certified to UNI CEI EN ISO/IEC 27001:2024+A1, the Italian adoption of ISO/IEC 27001:2022. The control titles follow the official English wording of the standard.
Nature of the document
This document forms an integral part of the supply contracts entered into with Clients and is referenced therein as a technical annex. For each contract, the binding version is the one published on the date of signature. In the event of any conflict between the provisions of this document and what is established in the body of the contract, the contractual conditions prevail.
This is a courtesy translation. The Italian version is the authoritative text: in the event of any discrepancy between language versions, the Italian version prevails.
Legend — Scope of application
Each control states, immediately below the title, the scope of application of the measure according to the following categories:
- All services
- Measure applied uniformly to every AtWorkStudio supply.
- IaaS · PaaS
- Cloud infrastructure and platform services.
- SaaS
- Application services delivered in cloud mode.
- Consulting
- Professional, systems and advisory services.
Current version
- Version
- 1.1
- Revision date
- June 2026
- Status
- In force
Preliminary note
Unless otherwise indicated in the service description, the additional services described in this document — including backup, log collection and management, encryption of data at rest and the collection of forensic evidence — are not included in the base supply and may be activated on request.
AtWorkStudio provides its services using datacentres certified to ISO/IEC 27001, ISO/IEC 27017 and ISO/IEC 27018, located in European Union countries, with guaranteed redundancy of power supply, cooling and connectivity.
ISO/IEC 27001:2022 · Theme 5
Organisational controls
5.1 Policies for information security
Scope · All services
AtWorkStudio adopts an Information Security Policy formally approved by Management, communicated to personnel and suppliers and reviewed at planned intervals and upon significant changes in the operating context. The policy is consistent with the requirements of ISO/IEC 27001:2022, ISO/IEC 27017:2015 and ISO/IEC 27018:2025 and constitutes the Provider's formal commitment to Clients and interested parties regarding information security.
5.2 Information security roles and responsibilities
Scope · All services
Information security roles and responsibilities are assigned to Management, which directly manages, implements and verifies all activities of the Information Security Management System. In its relationships with Clients, AtWorkStudio acts as Data Processor pursuant to Article 28 of Regulation (EU) 2016/679 (GDPR).
5.5 Contact with authorities
Scope · All services
Management maintains contact with the authorities relevant to the provision of the services, including the Italian Data Protection Authority (Garante per la Protezione dei Dati Personali), the ACN (Italian National Cybersecurity Agency), the Postal Police and the judicial authority. Institutional communications take place through official channels (PEC or certified mail). The notification of any personal data breaches to the Data Protection Authority takes place within 72 hours pursuant to Article 33 of the GDPR.
5.7 Threat intelligence
Scope · All services
Within its Management System, AtWorkStudio collects and analyses information on threats to information security, drawing on official sources (CVE, vendor portals, threat intelligence centres) and specialist aggregators. Relevant information is contextualised against the Provider's operating environment and, where necessary, leads to the updating of the risk assessment and of the technical measures. Customised threat intelligence services or reporting dedicated to the Client are provided under a separate contractual basis.
5.12 Classification of information
Scope · All services
Information is classified according to its confidentiality, integrity and availability and to the applicable legal, regulatory and contractual requirements. The technical and organisational protection adopted is proportionate to the classification. Protection levels are reviewed periodically depending on the relevance of the information and on regulatory compliance.
5.13 Labelling of information
Scope · All services
The labelling of information is implemented through cloud data classification and protection tools, consistently with the classification scheme adopted. Information with controlled access is managed on protected platforms and subject to traceability.
5.15 Access control
Scope · All services
Physical and logical access control to information and corporate assets is established according to the principle of least privilege. Logical access is managed through a centralised cloud identity management platform, with differentiated access by role, authorised by Management and protected by mandatory multi-factor authentication. Access profiles are reviewed periodically and promptly revoked at the end of the relationship.
5.16 Identity management
Scope · All services
The identity lifecycle is managed centrally through a cloud identity management platform. The creation, modification and deactivation of accounts take place upon formal authorisation by Management. The uniqueness of credentials is ensured, shared accounts are not permitted and, upon termination of the relationship, identities are deactivated immediately.
5.17 Authentication information
Scope · All services
Access credentials are managed centrally with mandatory multi-factor authentication. Passwords are not communicated in clear text and, where necessary, are stored in encrypted vaults. The assignment and revocation of credentials take place upon formal authorisation by Management.
5.18 Access rights
Scope · All services
Access rights are assigned exclusively upon authorisation by Management and according to the operational role, with segregation of privileges and traceability of activities. Upon termination of the assignment, rights are revoked immediately. Self-modification of access levels by users is not permitted.
5.19 Information security in supplier relationships
Scope · All services
Suppliers are classified, assessed and managed according to a formal procedure that provides for division into three categories (cloud, systems, occasional) based on the relevance of the service, the criticality for the Management System and the presence of certifications. Strategic suppliers are recorded in a dedicated list and, for those not ISO/IEC 27001 certified, a documented audit is conducted at least every two years.
5.20 Addressing information security within supplier agreements
Scope · All services
Agreements with suppliers include specific security clauses: non-disclosure agreements (NDAs), logging requirements, traced access, multi-factor authentication, encryption, restoration and confidentiality, in line with the ISO/IEC 27017 and ISO/IEC 27018 guidelines. Logical access by suppliers to the systems is protected by MFA and recorded in the system logs.
5.21 Managing information security in the ICT supply chain
Scope · All services
Critical suppliers are monitored at least annually through the review of the list and the verification of the continued existence of security, regulatory and contractual requirements. Changes in the corporate structure, in the location of datacentres or in the GDPR qualification (e.g. Processor / Sub-processor) are subject to specific assessment and, if relevant, lead to the updating of the contractual and technical documentation.
5.22 Monitoring, review and change management of supplier services
Scope · All services
AtWorkStudio monitors changes in suppliers' security practices and service terms through official portals, technical feeds and contractual communications. Relevant changes are assessed by Management and, if necessary, lead to updates in technical configurations, protection measures or contractual clauses towards Clients.
5.23 Information security for use of cloud services
Scope · IaaS · PaaS · SaaS
The acquisition, use and exit from cloud services provided or managed on behalf of Clients are governed contractually. AtWorkStudio applies security criteria consistent with its own Management System throughout all phases of the cloud service lifecycle, including access control, encryption, logging and segregation of responsibilities. Evidence of cloud providers' compliance (ISO/IEC 27017, ISO/IEC 27018 certifications, DPA) is available to Clients on request.
5.24 Information security incident management planning and preparation
Scope · All services
The management of information security incidents is governed by a formal procedure that defines roles, operational phases, tools used and tracking methods. Activation may take place upon a Client's report or through alerts from the monitoring systems (SIEM, EDR). The classification of events includes the assessment of the impact on personal data and any obligations to notify the Data Protection Authority pursuant to the GDPR.
5.26 Response to information security incidents
Scope · All services
The response to incidents is prompt and proportionate to the severity identified. All actions carried out are traced and, in the event of an impact on services provided or on personal data, communication towards the Client is activated according to the applicable contractual and regulatory rules. Incidents are classified into the following four levels:
Low level
No significant impact on service availability, no SLA breach, no personal data involved. Internal technical handling and recording in the tracking system, without proactive communication to the Client.
Medium level
Interruption or degradation of the service with limited impact contained within the contractual thresholds. The Client is informed where the impact is perceptible or the estimated duration of the interruption may exceed four hours.
High level
Significant interruption of the service, exceeding of the SLA thresholds or impact on multiple critical services. Formal communication to the Client indicating the corrective measures adopted and the restoration timescales.
Critical level
Significant compromise of the availability or integrity of the services involving personal data. The measures for the technical management of the incident and the procedures envisaged for the management of data breaches apply jointly, including any notifications to the Client Controller and to the competent Authority within the time limits set by law.
5.28 Collection of evidence
Scope · All services
Evidence relating to incidents is collected and retained through the active security systems (SIEM, EDR, MDM). Logs and events are recorded automatically and, where necessary, exported and archived in digital format to support internal, disciplinary or legal activities in compliance with the regulations in force. The service of collecting forensic evidence on the Client's systems is not included in the base supply and may be activated on request.
5.29 Information security during disruption
Scope · All services
Information security is ensured even during operational disruptions thanks to the adoption of resilient cloud platforms and technical measures that do not depend on local infrastructure. All critical assets remain protected by encryption, multi-factor authentication and access segregation. A Business Continuity and Disaster Recovery Plan defines the actions to be taken in an emergency.
5.30 ICT readiness for business continuity
Scope · IaaS · PaaS · SaaS
The continuity of ICT services is ensured through resilient cloud solutions, distributed across certified datacentres located in the European Union. The Provider's critical systems are configured to be accessible even during local disruptions, thanks to automatic failover and geographic replication. The Provider's ICT readiness is tested periodically. For Clients who have contracted the backup service (control 8.13), restore tests on the Client's data are carried out and documented according to the agreed arrangements.
Drawing up a detailed Disaster Recovery plan tailored to the Client's systems — defining RTO and RPO, restore runbooks, scenarios and periodic tests — is not included in the base service and is available as a contractual option.
5.31 Legal, statutory, regulatory and contractual requirements
Scope · All services
The legal, regulatory and contractual requirements relevant to information security are identified, documented and integrated into the Management System in compliance with the GDPR, ISO/IEC 27001:2022 and the clauses signed with Clients and suppliers. The review of compliance takes place during the review of the System or in the event of a change in the technical or organisational scope.
5.33 Protection of records
Scope · All services
All corporate records, including procedures, contracts, logs and Management System documentation, are retained in digital format on cloud platforms protected by multi-factor authentication and granular permission management. Records are accessible only to authorised parties and protected against tampering, unauthorised release and accidental loss. Paper archives are not used.
5.34 Privacy and protection of personal identifiable information (PII)
Scope · All services
AtWorkStudio processes personal data exclusively for the provision of the contracted services, in its capacity as Data Processor pursuant to Article 28 of the GDPR. The protection of personal data is ensured by encryption, multi-factor authentication, access segregation, traceability and retention in certified cloud environments located in the European Union.
5.35 Independent review of information security
Scope · All services
The approach and effectiveness of the Management System are reviewed through internal audits planned annually, which may be activated on an extraordinary basis in the event of incidents or significant changes. The audits are conducted by a certified ISO/IEC 27001 Lead Auditor, external and independent of Management. The Provider is also subject to periodic third-party audits carried out by the certification body and to periodic checks by its own DPO pursuant to Article 39(1)(b) of the GDPR.
Other applicable controls
- 5.3 Segregation of duties
- Managed by Management with compensating measures of continuous logging, traceability of administrative activities and periodic audits, in view of the Provider's lean organisational structure.
- 5.4 Management responsibilities
- Management directly communicates information security responsibilities, verifies them and manages every critical activity through regular internal audits.
- 5.6 Contact with special interest groups
- AtWorkStudio maintains active update channels with qualified sources in the field of cybersecurity (vendor portals, threat intelligence feeds, certification bodies, technical communities). It is a member of Clusit (Italian Association for Information Security).
- 5.8 Information security in project management
- Security is integrated into the project lifecycle through a specific risk assessment and the adoption of proportionate measures; at the end, a report is drawn up with the evidence archived.
- 5.9 Inventory of information and other associated assets
- Centralised and up-to-date inventory of corporate assets (devices, cloud environments, consoles, managed tenants), with identification of owner, status, platform and classification according to the Business Impact Analysis.
- 5.10 Acceptable use of information and other associated assets
- The operational rules for the acceptable use of tools are established in an internal policy communicated to collaborators and distributed in the Provider's restricted area.
- 5.11 Return of assets
- Formalised procedure for the return and decommissioning of assets, with definitive deletion of information from devices and deactivation of access and licences.
- 5.14 Information transfer
- Corporate communications take place through channels protected by TLS and MFA; confidential data is encrypted before sending and, where necessary, accompanied by contractual clauses or NDAs.
- 5.25 Assessment and decision on information security events
- Security events are monitored through consoles (SIEM, EDR). The technical assessment determines whether the event should be classified as an incident pursuant to control 5.24.
- 5.27 Learning from information security incidents
- Relevant incidents feed into documented corrective actions, configuration updates and revisions of the risk assessment.
- 5.32 Intellectual property rights
- The ownership of software, configurations, scripts and documentation provided by AtWorkStudio is governed by the master supply contracts. Improper or unauthorised use is prohibited.
- 5.36 Compliance with policies, rules and standards for information security
- The compliance of the Management System with policies and standards is verified through periodic internal audits over the entire ISMS scope, with reports archived and assessed during the management review.
- 5.37 Documented operating procedures
- Operational activities relevant to security are governed by documented procedures, which are kept up to date and accessible to the assigned personnel, retained digitally and listed in an index of the Management System.
ISO/IEC 27001:2022 · Theme 6
People controls
6.3 Information security awareness, education and training
Scope · All services
Collaborators and suppliers operating on behalf of AtWorkStudio are trained and informed about the corporate policies and the operational responsibilities connected to information security. Training and update activities are documented. Updates are communicated upon procedural revisions or relevant changes in the scope of the Management System.
6.8 Information security event reporting
Scope · All services
A channel for the prompt reporting of security events is available, open to Clients, collaborators and internal personnel, via email, ticket or direct communication to Management. All reports are recorded, analysed and managed according to the incident management procedure, without hierarchical filtering levels, in order to ensure responsiveness and transparency.
Other applicable controls
- 6.1 Screening
- AtWorkStudio operates through qualified external suppliers and collaborators, selected on the basis of criteria of reliability, technical competence and professional reputation. The preliminary assessment of suppliers replaces pre-employment checks.
- 6.2 Terms and conditions of employment
- Relationships with collaborators and suppliers are governed by contractual agreements containing specific clauses on information security and on compliance with internal procedures.
- 6.4 Disciplinary process
- Breaches of security rules are treated as contractual non-compliance and may result in the termination of the relationship or exclusion from future assignments. The internal policy defines prohibited behaviours and consequences.
- 6.5 Responsibilities after termination or change of employment
- At the end of the relationship, access is revoked, assets are returned and the confidentiality obligations envisaged in the contracts and NDAs are maintained.
- 6.6 Confidentiality or non-disclosure agreements
- AtWorkStudio uses specific NDAs or confidentiality clauses integrated into contracts with collaborators, Clients and suppliers, defining protected information, permitted processing methods and post-termination validity.
- 6.7 Remote working
- Remote working provides access exclusively through cloud platforms with MFA, encrypted devices managed centrally via MDM, in compliance with a dedicated procedure.
ISO/IEC 27001:2022 · Theme 7
Physical controls
7.1 Physical security perimeters
Scope · All services
The provision of AtWorkStudio's services is based on an entirely cloud architecture: the processing and storage of Clients' data take place at the datacentres of providers certified to ISO/IEC 27001, ISO/IEC 27017 and ISO/IEC 27018, equipped with multiple physical security perimeters, multi-factor access control, continuous 24/7 monitoring and documented compliance. The productive physical perimeter is therefore defined by the selected datacentres, according to the contractual evidence made available to Clients. The Provider's operating premises do not host processing infrastructure or removable media containing Clients' data; the personnel's workstations are centrally managed devices, encrypted at operating-system level and protected by multi-factor authentication.
7.5 Protecting against physical and environmental threats
Scope · IaaS · PaaS · SaaS
The cloud-first architecture adopted ensures protection against physical and environmental threats through selected providers with certified geo-redundant datacentres. Corporate devices are encrypted and, in the event of damage, loss or theft, no corporate data is accessible in clear text. Operational continuity in the event of environmental events is governed by the Business Continuity and Disaster Recovery Plan.
7.10 Storage media
Scope · All services
AtWorkStudio does not use removable physical storage media for the processing or retention of corporate or Clients' data. All information resides on cloud systems or corporate devices protected by encryption, MFA and centralised management. The use of unauthorised external media is prohibited by the internal policy.
7.14 Secure disposal or re-use of equipment
Scope · All services
The disposal of assets provides for complete remote reset via MDM with secure removal of all data. Devices are not transferred to third parties without prior deletion of corporate information. Operational data resides on cloud platforms and there are no persistent local copies on the devices.
Other applicable controls
- 7.7 Clear desk and clear screen
- No paper or removable media containing corporate information are used. Devices are configured for automatic screen lock with biometric authentication.
- 7.8 Equipment siting and protection
- Corporate equipment consists of portable devices assigned exclusively to authorised personnel, used in private or controlled environments. There are no devices in public spaces or accessible to third parties.
- 7.9 Security of assets off-premises
- Assets used off-premises are protected by encryption, MDM management and biometric authentication. In the event of loss or theft, remote locking, location or wiping is possible.
- 7.13 Equipment maintenance
- The equipment in use is leased from the manufacturer, which guarantees hardware maintenance. Software management is carried out via MDM with centralised updating.
Controls not applicable
- 7.2 Physical entry
- Not applicable: the operating premises do not host servers, critical infrastructure or sensitive paper archives and are not open to the public. The protection of information is ensured exclusively at the logical level.
- 7.3 Securing offices, rooms and facilities
- Not applicable: AtWorkStudio does not have premises that can be classified as secure areas within the meaning of the standard.
- 7.4 Physical security monitoring
- Not applicable: the premises do not host servers or critical infrastructure and are not open to the public; the private and exclusive-use nature of the premises, combined with device encryption, makes the adoption of video surveillance systems unnecessary.
- 7.6 Working in secure areas
- Not applicable: there are no physical areas classified as secure; security is ensured at the logical level.
- 7.11 Supporting utilities
- Not applicable: there are no servers, critical infrastructure or fixed equipment requiring power continuity systems or dedicated auxiliary services.
- 7.12 Cabling security
- Not applicable: there is no complex cabling infrastructure or internal wired networks subject to interception risk. Internal communications take place over a wireless network protected by encryption compliant with industry standards.
ISO/IEC 27001:2022 · Theme 8
Technological controls
8.2 Privileged access rights
Scope · All services
Privileged access rights are limited to personnel authorised by Management. Administrative accounts are separated from operational accounts and protected by multi-factor authentication. Activities on the administrative environments (cloud productivity platforms, infrastructure, backup, MDM and network management) are traced and subject to centralised logging. There are no shared accounts or permanent elevated privileges for ordinary users.
8.3 Information access restriction
Scope · All services
Access to information is restricted according to the principle of least privilege. Permissions are assigned to specific operational roles and authorised by Management. Accounts are managed through the cloud identity management platform with mandatory MFA and all activities are traced in the cloud platforms' logs. Shared accounts or untraceable access are not permitted.
8.5 Secure authentication
Scope · All services
Access to cloud services and control panels is protected by mandatory multi-factor authentication. Mobile devices use biometric authentication and automatic locking. Credentials are personal, traceable and revoked upon termination of the relationship.
8.6 Capacity management
Scope · IaaS · PaaS · SaaS
Capacity management is ensured by the scalable cloud architecture of the providers adopted. Storage and backup are consumption-based according to the contractual conditions defined with the Client. Active monitoring of infrastructure resources may be offered as an optional service.
8.7 Protection against malware
Scope · All services
On the Provider's devices and systems, protection against malware adopts a multi-layered approach: Endpoint Detection and Response (EDR) solutions with behavioural detection, automatic containment of threats and centralised telemetry; native operating-system mechanisms that allow the installation only of software signed by certified developers; automatic updates of definitions and security policies distributed via MDM; correlation of events and response to alerts through SIEM. Personnel awareness is reinforced by continuous training and periodic awareness campaigns.
The extension of the same measures to the Client's devices, endpoints and systems (managed anti-malware/EDR, MDM, training) constitutes an additional service provided under a separate contractual basis.
8.8 Management of technical vulnerabilities
Scope · IaaS · PaaS · SaaS
Technical vulnerabilities on the Provider's systems are identified through the EDR console and official sources (CVE, vendor feeds) and managed according to a formal patch management procedure. The cloud infrastructure is subject to the security, updating and vulnerability management policies of ISO/IEC 27001 certified vendors.
For Clients who have contracted a managed patch management or vulnerability assessment service, the activities are provided according to the agreed arrangements and the evidence of system updates is archived in dedicated management portals, accessible to the Client.
8.9 Configuration management
Scope · IaaS · PaaS · SaaS
The security configurations of the Provider's devices and systems are managed according to documented baselines (encryption, automatic locking, automatic updates, MFA, backup, remote wipe). Compliance with the baselines is verified during the management review. For Clients who have contracted a managed cloud administration or systems service, the configurations of their systems are administered through the specific tools of each environment and traced through change management.
8.10 Information deletion
Scope · All services
Corporate or Clients' information is deleted when no longer needed, in compliance with the contracts, the data protection agreements (DPA) and the principles of Regulation (EU) 2016/679. Data is retained exclusively on cloud platforms equipped with automatic retention and secure deletion. During disposal, devices are reset according to procedure, with destruction of the encryption key for devices equipped with a dedicated security chip.
8.12 Data leakage prevention
Scope · All services
Data loss prevention (DLP) measures are implemented through device configurations, access segregation, encryption and managed cloud tools. Specific DLP policies can be activated through the data classification and protection tools available on the Client's cloud platforms, upon contractual request. User behaviour is governed by the internal policy.
8.13 Information backup
Scope · IaaS · PaaS · SaaS
Backup services are provided through selected enterprise cloud backup platforms, according to contracted arrangements. Backups are AES-256 encrypted and replicated in certified datacentres in the European Union. Integrity is ensured by centralised monitoring, retention policies and the possibility of restoring at various levels. The backup service is not included in the base supply and may be activated on request, defining with the Client the scope, frequency, encryption, retention, methods of verifying integrity, restore timescales and backup location.
8.14 Redundancy of information processing facilities
Scope · IaaS · PaaS · SaaS
Critical systems are hosted on cloud infrastructure with high availability, automatic failover and geographic replication. The cloud-native architecture eliminates internal single points of failure. Availability requirements are declared in the contracts with Clients with a contractual SLA of no less than 99.9%.
8.15 Logging
Scope · IaaS · PaaS · SaaS
Logs of relevant activities are collected and retained through centralised systems (SIEM, identity management platform, EDR, backup, network management consoles). The events traced include access, critical changes, errors, administrative operations and anomalies. Logs are protected against unauthorised access and used for the analysis of security events. The service of collecting and retaining access logs on the Client's systems (in compliance with the Data Protection Authority's provisions on System Administrators) is not included in the base supply and may be activated on request.
8.16 Monitoring activities
Scope · IaaS · PaaS · SaaS
On the Provider's systems and networks, continuous monitoring activity is operated through SIEM for the detection of anomalous behaviours and potential incidents, and through a network security console for the monitoring of the local network. The native consoles of the cloud services provide further alerts on relevant events.
Managed monitoring services for the Client's systems (SIEM-as-a-Service, MDR, customised alerting) are provided under a separate contractual basis.
8.18 Use of privileged utility programs
Scope · All services
The use of privileged utility programs is limited to authorised personnel and traced in the platforms' logs. High-impact system tools are accessible only with administrative accounts protected by MFA, and their use is subject to logging and direct authorisation by Management. Where it is necessary to access cloud systems with utility programs (antivirus, IDS, IPS, vulnerability assessment software), the Provider reserves the right to do so without prior notice to the Client.
8.20 Networks security
Scope · All services
Internal networks are protected by encryption, segmentation and controlled authentication through a centralised network management console. Devices are individually authorised and managed via MDM. Data in transit is protected by TLS/HTTPS encryption.
8.21 Security of network services
Scope · All services
The accessible cloud services ensure the protection of traffic through TLS and secure authentication mechanisms. The service levels of the connectivity and cloud providers are monitored through their respective consoles.
8.22 Segregation of networks
Scope · IaaS · PaaS · SaaS
Network segregation is implemented through configured VLANs and separate SSIDs for management, corporate devices and services. Traffic between segments is restricted through firewalls and centralised rules. Access is permitted only to managed and authorised devices. The network on which the machines providing the services are located is virtually and/or physically segregated from the Provider's other networks.
8.24 Use of cryptography
Scope · All services
Cryptography is applied to data at rest and in transit. Corporate devices are encrypted natively at operating-system level and through a dedicated security chip. Data in transit travels over TLS/HTTPS channels and backups are protected with AES-256 encryption. At the Client's request, Bring Your Own Key (BYOK) solutions can be activated. Emails containing confidential data can be encrypted through cloud message protection tools. The encryption of data at rest for the Client's services is not included in the base supply and may be activated on request. The Provider and its partners keep the encryption keys in a secure location.
8.32 Change management
Scope · All services
Changes to configurations, cloud systems, devices and services are managed through a formal change management model. Each variation is documented, approved by Management and linked to any security impact assessments. Variations that may impact the Client are communicated indicating the type of change, the date and expected timing, the technical description and the notification of the start and end of the intervention. In the event of a proven emergency problem, including one related to data security, the Provider has the right to interrupt the provision of the services in whole or in part in order to protect the Client's structure, service and data.
Other applicable controls
- 8.1 User end point devices
- Information is accessible exclusively from corporate devices configured via MDM, protected by encryption, biometric authentication and automatic locking. Access to data takes place through cloud services protected by MFA and logging.
- 8.11 Data masking
- No real data is used in test environments. On the Client's cloud productivity platforms, data masking mechanisms or confidentiality labels can be activated through the native data classification and protection tools, upon contractual request.
- 8.17 Clock synchronization
- All information systems are synchronised through official NTP servers managed natively by the respective cloud providers or by primary international NTP servers.
- 8.19 Installation of software on operational systems
- Devices accept only applications digitally signed by certified developers. The installation of software is reserved for administrative personnel and configurations are enforced via MDM.
- 8.23 Web filtering
- AtWorkStudio uses secure DNS configured on the network and devices, capable of automatically blocking malicious domains, phishing and non-compliant content.
- 8.26 Application security requirements
- Security requirements (authentication, cryptography, logging) are assessed during the acquisition or configuration of each application adopted, as part of the supplier selection process.
- 8.27 Secure system architecture and engineering principles
- System implementation projects follow the principles of secure architecture: perimeter, strong authentication, logging, access segregation, data encryption, least privilege and operational resilience.
- 8.31 Separation of development, test and production environments
- For Clients who request it, AtWorkStudio creates and manages separate cloud environments for the development, test and production phases, ensuring isolation between the environments in accordance with the contract.
- 8.33 Test information
- No real data is used in tests. Test information is created artificially or anonymised, used only in separate and temporary environments and not retained beyond the duration of the test.
- 8.34 Protection of information systems during audit testing
- Technical verification activities (including Vulnerability Assessments) are planned and traced to avoid impacts on active processes. External audits do not have direct access to the systems and are supervised by internal personnel.
Controls not applicable
- 8.4 Access to source code
- Not applicable: software development is not within the scope of AtWorkStudio's certification.
- 8.25 Secure development life cycle
- Not applicable: software development is not within the scope of the certification.
- 8.28 Secure coding
- Not applicable: software development is not within the scope of the certification.
- 8.29 Security testing in development and acceptance
- Not applicable: software development is not within the scope of the certification.
- 8.30 Outsourced development
- Not applicable: software development is not within the scope of the certification.
ISO/IEC 27017:2015 · Annex A
Cloud service-specific controls
The following controls supplement those of ISO/IEC 27001:2022 with requirements specific to the provision of cloud services, in the role of Cloud Service Provider.
CLD.6.3.1 Shared roles and responsibilities within a cloud computing environment
Scope · IaaS · PaaS · SaaS
The roles, responsibilities and capabilities required for the use of cloud services are documented and communicated to Clients in the service contracts, which clearly define what falls to the Provider and what remains with the Client for each service model provided (IaaS, PaaS, SaaS).
CLD.8.1.5 Removal of cloud service customer assets (exit strategy)
Scope · IaaS · PaaS · SaaS
The service contracts provide for an exit strategy that defines the timing and methods for the return of data, the assets subject to return and the procedure for communicating deletion or return. Decommissioning requests are recorded in the ticketing system and execution times are monitored against the contractual deadlines. The Client may request a paid exit strategy service that defines the components included, the activities to be carried out, the parties involved, the release dates and the time period. In the event of decommissioning, the Provider carries out the complete deletion of all data within 30 days of the Client's request, providing evidence by means of a decommissioning report.
CLD.9.5.1 Segregation in virtual computing environments
Scope · IaaS · PaaS · SaaS
Each Client has its own tenant or resource group logically separated from the others. The Provider ensures the separation of internal administration environments from the resources used for the provision of services to the Client and implements security controls that ensure an appropriate isolation of the resources used by the different tenants.
CLD.9.5.2 Virtual machine hardening
Scope · IaaS · PaaS
The hardening of virtual machines is carried out according to the specifications documented in the Client's contract, using the provider's standard security settings as a starting point (minimum ports, minimum services, anti-malware, log monitoring). The security configurations are defined and maintained for each Client.
CLD.12.1.5 Administrator's operational security
Scope · IaaS · PaaS · SaaS
The procedures for critical administrative operations (installation, modification or deletion of virtual resources, contract termination procedures, backup and restore) are documented in the service contracts and operational procedures. For Clients who have contracted the operational management of their cloud environments, protection mechanisms (resource locks) are activated, where technically applicable, to prevent unauthorised deletions or modifications of critical resources.
CLD.12.4.5 Monitoring of cloud services
Scope · IaaS · PaaS · SaaS
Cloud monitoring capabilities are available to Clients through the providers' native consoles, with exclusive access to their own data. The monitoring service managed by AtWorkStudio is offered as an optional service on a contractual basis. The documentation on the available monitoring capabilities is accessible directly from the administration panels of each service.
CLD.13.1.4 Alignment of security management for virtual and physical networks
Scope · IaaS · PaaS
The configuration of virtual networks is designed to measure for each Client based on the agreed requirements and project specifications, when the service is contracted. The alignment between virtual and physical configuration is ensured by the design process and maintained over time through change management.
ISO/IEC 27018:2025 · Annex A
Protection of personally identifiable information (PII) in public cloud
The following controls supplement those of ISO/IEC 27001:2022 with additional requirements applicable to public cloud service providers that process personally identifiable information (PII) in their capacity as Data Processor pursuant to Article 28 of the GDPR.
A.3.1 Consent and choice
Scope · IaaS · PaaS · SaaS
The personal data present in the cloud is processed exclusively for the purposes defined by the Client in the appointment as Data Processor. The Provider does not carry out any processing additional to or different from that instructed by the Client Controller.
A.3.2 Purpose legitimacy and specification
Scope · IaaS · PaaS · SaaS
The personal data processed as part of the provision of the services is not in any case used by the Provider for marketing or advertising purposes. The appointment as Data Processor expressly excludes any use of the data outside the instructions of the Client Controller.
A.10.1 Notification of a personal data breach
Scope · IaaS · PaaS · SaaS
In the event of a personal data breach, the Provider promptly notifies the Client Controller, providing all the information necessary so that the Client can fulfil its own notification obligations to the competent Authorities within the time limits set by the GDPR. The security event management procedure defines the classification, timing and methods of communication.
A.11.11 Contractual measures
Scope · IaaS · PaaS · SaaS
The contracts between AtWorkStudio and Clients define the minimum technical and organisational measures applied to the processing of personal data, consistently with the instructions of the Data Controller. The measures are not subject to unilateral reduction by the Provider.
A.11.12 Sub-contracted PII processing
Scope · IaaS · PaaS · SaaS
Any recourse to sub-suppliers that process personal data is governed by the appointment as Data Processor or by the contractual agreements with the suppliers, which impose security and data protection obligations no lower than those applied by the Provider to the Client. The sub-suppliers are assessed and monitored within the supplier management process.
A.12.1 Geographical location of PII
Scope · IaaS · PaaS · SaaS
The personal data processed on behalf of Clients is hosted in datacentres located in the European Union. The exposure to the non-EU jurisdiction of the cloud providers adopted is subject to specific assessment and documented in the Management System. The Client is informed of the countries in which the data may be processed through the contractual evidence and the appointment as Processor.
Other applicable controls
- A.2.1 Obligation to co-operate regarding PII principals' rights
- The Provider makes available to the Client the tools and evidence necessary for the exercise of the rights of data subjects pursuant to the GDPR, consistently with the appointment as Data Processor.
- A.5.1 Secure erasure of temporary files
- The deletion of temporary files is managed contractually with the Client as part of the protection measures applied to the cloud platform.
- A.6.1 Notification of legally binding requests for disclosure of PII
- In its capacity as Processor, AtWorkStudio discloses personal data only to the public security authorities or to the judicial authority that make a legitimate request for it, and to the parties formally indicated by the Client Controller.
- A.6.2 Recording of PII disclosures
- No disclosure of personal data takes place except in the cases provided for by control A.6.1; any disclosures are recorded.
- A.8.1 Disclosure of sub-contracted PII processing
- Recourse to sub-processors is governed in the appointment as Data Processor, with the obligation of prior authorisation by the Client and the signing of specific NDAs.
- A.10.2 Retention period for administrative security policies and guidelines
- Historical copies of the Management System policies and procedures are retained by Management for a period adequate to allow subsequent verifications, disputes and investigations by the competent Authority.
- A.10.3 PII return, transfer and disposal
- The methods for the return, transfer and disposal of personal data at the end of the contract are defined in the appointment as Data Processor and, for the operational component, in the exit strategy described in control CLD.8.1.5.
- A.11.1 Confidentiality or non-disclosure agreements
- The Provider's collaborators with access to personal data are bound by confidentiality obligations formalised in the contracts and NDAs, which survive the termination of the relationship.
- A.11.2 Restriction of the creation of hardcopy material
- The creation of hardcopy material containing personal data is restricted according to what is defined by the information classification provided for by the internal policy.
- A.11.3 Control and logging of data restoration
- Data restoration activities are traced and logged according to the Business Continuity and Disaster Recovery Plan.
- A.11.4 Protecting data on storage media leaving the premises
- The transfer of data takes place exclusively through network channels protected by encryption; no physical storage media leaving the premises are used.
- A.11.5 Use of unencrypted portable storage media and devices
- The transfer of data takes place exclusively through network channels protected by encryption; the use of unencrypted portable media is not envisaged.
- A.11.6 Encryption of PII transmitted over public data-transmission networks
- Personal data transmitted over public networks is protected by TLS/HTTPS encryption with a valid certificate.
- A.11.7 Secure disposal of hardcopy materials
- The methods for the secure disposal of any hardcopy material are provided for by the internal policy.
- A.11.8 Unique use of user IDs
- Each user has a unique identifier, as provided for by the physical and logical access procedure.
- A.11.9 Records of authorized users
- The list of users authorised to access the systems is maintained and updated by Management.
- A.11.10 User ID management
- The management of user IDs is governed by the internal policy and by the physical and logical access procedure, including creation, modification, suspension and revocation.
- A.11.13 Use of storage spaces previously used
- The segregation of tenants and resources ensures that storage spaces previously used by other Clients are not accessible to different Clients.
- A.12.2 Intended destination of PII
- The connection between the Client and the virtualised resources hosted in the datacentres takes place using the HTTPS protocol, where required, ensuring the integrity and confidentiality of the transport.
Version history
- 1.1 — June 2026
- Clarified that the detailed Disaster Recovery plan tailored to the Client's systems is a service available on a contractual basis (control 5.30). Published the English and German versions, with a clause indicating the Italian version as the authoritative text.
- 1.0 — April 2026
- First publication of the document in the structure aligned with the controls of ISO/IEC 27001:2022 Annex A, integrated with ISO/IEC 27017:2015 (Annex A) for cloud services and with ISO/IEC 27018:2025 (Annex A) for the processing of personal data in public cloud.