Business guides – contracts, HR, AI & compliance

AI, cybersecurity, and IT agreements – a guide for companies

Comprehensive guide to AI governance, AI policy, GDPR/DPA, SaaS agreements, NIS2, supplier security, BIA, and business continuity planning for companies.
Published Mallbutiken
AI, cybersecurity, and IT agreements – a guide for companies

By Mallbutiken · Facts checked September 30, 2026 · Approx. 12 minutes reading time

AI, data protection, SaaS agreements, NIS2, and continuity are not separate islands of documentation. They converge on the same practical issues: which systems may be used, what data may be processed, what requirements should be imposed on the supplier, who is responsible for the risks, and how does the business continue if the service disappears?

Use this page as a map: start with the actual process or technology and then select the right policy document, agreement, and control. A company rarely needs "every template." It needs the documents that correspond to its actual roles, data, suppliers, and risks.

Which document solves which issue?

Issue Document or process Deep dive
How can employees use AI? AI policy AI policy for companies
Which AI systems do we have and what are their risks? AI register, role and risk assessment, governance AI Governance package
Does the supplier process personal data for us? Role assessment and, if necessary, DPA Data Processing Agreement (DPA)
What should a cloud service deliver? SaaS agreement, SLA, security and exit attachments SaaS agreements
How do we handle supply chain risk? Supplier classification, security requirements, and follow-up NIS2 and supplier agreements
What must be restored first after a disruption? BIA / impact analysis BIA step by step
How do we continue when normal operation fails? Continuity plan and backup routines Continuity plan

AI policy and AI governance: manage usage and system risk separately

An AI policy primarily answers user questions: which tools are approved, what information may be entered, when is human oversight required, how is external publishing handled, and what does the employee do in the event of an incident?

AI governance is broader. There, the organization needs to be able to inventory AI systems, identify its role under the AI Act, assess use cases, assign responsibility, and follow up on suppliers and changes over time.

AI policy

Operational rules for employees and business.

  • Approved tools
  • Data and confidentiality
  • Human oversight
  • AI literacy
  • Incident reporting

AI governance

Management and control of the organization’s AI portfolio.

  • AI register
  • Role assessment
  • Risk classification
  • Supplier assessment
  • Decision-making and follow-up

The EU AI Act is risk- and role-based. Therefore, it is misleading to think that a single document "makes the company AI Act-compliant." The documentation needs to reflect which systems the organization actually develops, provides, or uses.

AI and personal data overlap quickly

If an AI tool processes personal data, AI governance needs to be linked to GDPR processes. Check, among other things, purpose, legal basis, personal data roles, data minimization, third-country issues, and whether a Data Protection Impact Assessment (DPIA) under GDPR might be necessary.

GDPR and DPA: start with the actual role

It is easy to treat the DPA as an attachment that should always be sent to an IT supplier. The correct first step is instead to assess who determines the purposes and means of the personal data processing.

When the supplier processes personal data on the customer's behalf, Article 28 of the GDPR and binding regulation for the processor's treatment are triggered. The agreement needs to handle, among other things, instructions, security, sub-processors, support for the controller, erasure/return, and audit rights.

A DPA is not a "get out of jail free" card. A correct Data Processing Agreement does not replace legal basis, transparency, data minimization, or the rules regarding international transfers.

SaaS agreements: tie together service, data, security, and exit

A SaaS agreement should not stop at price and license. For a business-critical service, the main agreement needs to work in tandem with the service specification, SLA, personal data, security requirements, subcontractors, liability, and exit strategy.

Ask, for example:

  • What exactly is included in the subscription?
  • How is availability measured?
  • Which incident levels and response times apply?
  • Where is data located and which subcontractors are used?
  • Which security controls can be verified?
  • How can the customer export data and leave the service?

If the service processes personal data, the SaaS agreement is linked to the DPA. If the customer is subject to the Cybersecurity Act, security and supply chain requirements may need to be further tightened.

NIS2 and the Cybersecurity Act: the supplier is part of the risk profile

The Swedish Cybersecurity Act (2025:1506) entered into force on January 15, 2026. For organizations subject to the Act, security measures must include risk analysis, incident management, operational continuity and crisis management, supply chain security, security during acquisition/development/maintenance, follow-up, cyber hygiene, cryptography, and access control.

This makes supplier management more than just a purchasing issue. The organization needs to know which suppliers are critical, what dependencies they have, how incidents are communicated, and how security requirements are followed up.

Not all suppliers need the same requirements

The work should be risk-based and proportionate. A marketing tool without sensitive data and an operating system that the entire core business depends on should not automatically be treated identically.

Therefore, build a simple supplier classification based on access, data sensitivity, operational dependency, concentration risk, and recovery. Let the classification guide due diligence, contractual requirements, and follow-up.

BIA and continuity plan: from requirements to actual resilience

Cyber and supplier requirements only help partially if the organization does not know which activities are most critical. A BIA (Business Impact Analysis) maps business-critical activities, consequences over time, and the resources that the activities require.

Subsequently, continuity plans are built to be able to continue or restore these activities when normal resources are not functioning.

BIA

Answers what and how quickly.

  • Critical activities
  • Consequences over time
  • Dependencies
  • Tolerable downtime
  • RTO/RPO and prioritization

Continuity plan

Answers how the business acts.

  • Activation
  • Roles
  • Backup routines
  • Communication
  • Recovery and return

The Swedish Civil Contingencies Agency's (MSB) methodology support describes impact analysis, risk assessment, measures, and continuity planning as parts of a coherent continuity effort.

A practical workflow for companies

  1. Inventory. List critical processes, IT services, AI systems, data flows, and suppliers.
  2. Classify. Which information and activities are most worthy of protection or time-critical?
  3. Assess roles and legal requirements. GDPR role, AI Act role, NIS2 application, and any sector-specific requirements.
  4. Prioritize gaps. Start where actual risk and business impact are greatest.
  5. Govern internally. Policies, roles, approvals, and training.
  6. Regulate externally. SaaS, DPA, security, and other supplier terms.
  7. Plan for disruptions. BIA, backup routines, and continuity plan.
  8. Test and follow up. Documentation should lead to measurable control and improvement.

Example: the company introduces an AI-based HR system

One single purchase may require several perspectives. AI governance assesses the system's AI usage and risk. The AI policy states which functions employees may use. The GDPR assessment maps personal data and roles. The SaaS agreement regulates service, SLA, and exit. The DPA regulates processor treatment. The security assessment reviews access and the supply chain. The BIA determines how critical the system is for the business, and the continuity plan describes the backup routine if the system is down.

The point is not to create the maximum volume of documentation. The point is that the same actual system should be consistently managed in all relevant governance and contractual layers.

Management checklist

  • Do we know which AI systems and critical IT services are actually used?
  • Is there an owner for every critical system and supplier?
  • Have personal data roles and data flows been documented?
  • Have we checked which systems may contain confidential information?
  • Are there measurable SLA and security requirements where the business depends on the supplier?
  • Are critical subcontractors and third-country flows known?
  • Has the business identified its most time-critical activities?
  • Are there realistic backup routines and recovery targets?
  • Are continuity and security tested in practice?
  • Is there a routine for changes: new AI functions, suppliers, integrations, and contractual terms?
  • Does management receive recurring reporting on risks, incidents, and open actions?
AI Governance and AI Act compliance package with AI register and risk assessment

Do you need to structure AI governance?

Mallbutiken's AI Governance package contains six Word/PDF templates and an AI register in Excel for system inventory, risk assessment, supplier control, and governance, among other things. Price in shop: 199 SEK.

See the AI Governance packageSee AI templates

Deep dive by area

Templates in this article

Explore the topic