Lexology GTDT Market Intelligence provides a unique perspective on evolving legal and regulatory landscapes. This interview is taken from the Digital Transformation volume discussing various topics, including a look at the main laws and regulations, the impact of cybersecurity legislation, cloud contract considerations, the impact of data protection laws and more, within key jurisdictions worldwide.

1 What are the key features of the main laws and regulations governing digital transformation in your jurisdiction?

For most Norwegian organisations, digital transformation is mainly affected by the same general technology-centric laws and regulations that apply in other European jurisdictions. This includes the GDPR, the e-privacy directive and the web accessibility directive. The emergence of big data cooperations between Norwegian businesses has also increasingly put an emphasis on the competition law implications of such synergies in digital transformation projects.

For organisations belonging to a specific industry or business sector, for example, finance, health, telecommunications or industries of particular national interest, additional sector-specific national laws and regulations must also be taken into account. These laws and regulations may, for example, place increased importance on reviewing and assessing the cybersecurity implications of any planned transformation, by penalising an organisation’s failure to implement adequate information security measures. They may also place restrictions on an organisation’s ability to outsource IT operations or business functions.

For the most part, these regulations emphasise self-governance, placing the onus of compliance on the organisations themselves. This means that they are generally left to conduct their own assurance of compliance with their sector-specific requirements, rather than being able to attain and rely on governmental approvals. Failure to conduct the required diligence operations in a responsible manner, may subsequently be penalised in the form of fines or, in particularly egregious circumstances, imprisonment. Some exceptions to the self-governance features do apply, for example with respect to government approvals or notification procedures with respect to outsourcing in certain sectors.

Organisations affected by these national requirements may also need to be aware of, and take into account, sector-specific notification requirements, for example, cybersecurity breaches which apply in addition to the general requirements under the GDPR.

2 What are the most noteworthy recent developments affecting organisations’ digital transformation plans and projects in your jurisdiction, including any government policy or regulatory initiatives?

As with most other jurisdictions, the ongoing pandemic has required many organisations to rethink and evolve their work setup to maintain productivity and a healthy working environment, while doing their part to comply with the various government restrictions.

Transitioning from a traditional office-based infrastructure to a more Agile and ‘remote-first’ approach means that existing solutions, primarily intended as secondary or provisional options, have been put under increased strain. This in turn has required investment in new and improved digital tools and infrastructure.

Although Norwegian organisations in some ways have been somewhat ahead of the curve in terms of transitioning to a more flexible and decentralised working environment, many saw need for further improvement when the time came to ‘flip the switch’ in the spring of 2020.

In this respect, the current environment has been an accelerator within digitisation, as many organisations have had to speed up and expand their ongoing digital transformation initiatives. We have seen this in maintained and increased activity within digital transformation projects and technology procurements, both on the customer and supplier side. Our impression has been that already planned and ongoing transformation projects have been maintained throughout this period, and that technology procurements have been prioritised by organisations despite the general uncertainties regarding the economic outlook in most markets.

The current period has also brought with it an increase in cyberattacks on Norwegian organisations. The attacks primarily exploit what is often the weakest link in any information security setup − human error. This has demonstrated the importance of taking a more holistic approach to transformation projects, and highlighted that a successful digital transformation goes beyond mere technology procurement. Employee training and awareness building has had a revived focus, as organisations have developed increased awareness that this is and remains the first line of defence against cyberattacks, regardless of how substantial and advanced the technological security mechanisms may be.

Beyond the current circumstances, which have affected most of 2020, GDPR enforcement has brought increased awareness to the data protection implications of digital transformation. Innovative and advanced digital solutions often involve new and increased personal data processing operations, which organisations are increasingly addressing and assessing prior to implementations rather than after the fact (as has often been the case previously). We have also seen this awareness result in increased demands being placed on the suppliers in digital transformation projects to demonstrate GDPR compliance and how they can help organisations meet their own compliance requirements. A risk associated with the latter observation, as perceived from the supplier side, is that some organisations may seek to overly rely on their suppliers for their own compliance measures.

A general trend which has continued in the recent climate, is the expansion of digital partnerships between organisations, both vertical and among peers, in more traditional market segments and innovative technology specialists to enter into new markets and business sectors. This includes major actors within insurance, finance and real estate leveraging market insight and data in partnerships with technology specialists to develop and offer new products and services within data analytics.

3 What are the key legal and practical factors that organisations should consider for a successful Cloud and data centre strategy?

The migration from on-premise and legacy based systems to cCloud environments and software-as-a-service (SaaS) continue to dominate IT strategies in most Norwegian organisations.

Key drivers for this continuous shift remain the same; businesses seek to achieve lower operational and capital costs, access to better, more modern technology and accelerate the development and rollout of new products and services in response to constantly changing external and internal demands.

However, certain operations require a closer proximity and better control over the computing resources than public cloud services typically offer. Such requirements may stem from regulatory requirements and business-driven requirements. In those circumstances, a more traditional data centre strategy may be required.

The push towards more cloud solutions and the pull towards more traditional data centre solutions therefore typically calls for a diversified computing and data storage strategy in most organisations.

In highly regulated sectors, we have traditionally seen a reluctance to use public cloud services. However, as cloud service providers mature and develop more tailored services to various sectors, we see an increasing adoption of cloud services even in highly regulated sectors such as financial services and insurance.

From a practical perspective, considering the demands of the business will be key in establishing a successful cloud and data centre strategy. Some typical and important considerations to be made include: suitability for the public cloud, including whether legacy systems can be supported by modern cloud platforms; support and managed services capabilities of the cloud provider; information security and business criticality may intuitively drive a data centre strategy, but may actually be better served by a cloud provider; the need for proximity to the computing resource may dictate an on-premise solution rather than cloud;and hidden costs: the cloud comes with a promise of reduced costs and utility pricing models, while the reality often reveals establishment costs and long-term volume commitments sometimes rendering the cloud service equally (or more) expensive than traditional models.

From a legal standpoint, cloud migration and data centre strategies will be impacted by the regulatory landscape in which the business operates. Norwegian financial institutions and other regulated entities will typically have to observe both local and European regulatory guidelines and requirements pertaining to outsourcing and cloud migration, including local requirements set out in the Norwegian ICT regulations, sector-specific EU law as well as guidelines laid down by industrial bodies such as European Banking Association (EBA) and European Insurance and Occupational Pensions Authority (EIOPA) to mention a few.

Similarly, certain Norwegian data storage requirements may impact what type of data is being processed and stored in data centres outside of Norway or the EEA.

Data protection and cybersecurity laws remain important factors to consider in any company’s cloud and data centre strategies. Assessments regarding data location should be made as to whether certain data should be stored within Norway (due to, for example, regulatory requirements, sector guidelines or contractual commitments) and whether the cloud provider relies on data processors outside the EEA. The latter is increasingly becoming an area of focus after the Schrems II judgment having invalidated the Privacy Shield and requiring assessment of the privacy risk level in the country where the processing takes place despite using EU’s standard contract clauses for transfer of data, thus creating a significant amount of uncertainty with regard to how Norwegian businesses can continue to use cloud providers with data centres or support functions outside of the EEA.

Other elements of importance for implementing a successful cloud and data centre strategy include having a well-considered view on the use of subcontractors.

The inclusion of customer and third-party audit rights have been a source of controversy in negotiations with cloud providers for quite some time, particularly as Norwegian financial regulations traditionally have not been accommodating to more restrictive audit rights. As both data centre providers and regulators mature, this is now normally an issue which is resolved between the parties.

4 What contracting points, techniques and best practices should organisations be aware of when procuring digital transformation services at each level of the Cloud ‘stack’? How have these evolved over the past five years and what is the direction of travel?

Procurement of digital transformation services, irrespective of which level of the cloud stack, raises several similar challenges.

A common challenge relates to the existence of incompatible interests between the transformation partner and the customer, which causes friction in the execution of the project. In order to address this, it is key that the contract is drafted to ensure that both parties’ interests are addressed and aligned to the extent possible. Ideally, common incentives to achieve the intended business goals in the transformation project should be explored, for example by using charging models geared towards achievement of certain business goals (eg, achieving a defined business case for the transformation). While this is a tempting proposition, reality often show that such models are difficult to use in practice as they require a level of control by the vendor over the customer’s value chain, priorities and ability to execute on the transformation enablers (such as staff reductions).

The commercial model and the delivery model (methodology) should also be carefully aligned. Almost every transformation project uses Agile project methodologies, simply because the development of the requirements forms a central part of the transformation process. At the same time, most businesses want budget certainty for the transformation initiative. However, the scope of flexibility required in an Agile development model is not necessarily compatible with the rigidity of a fixed-price commercial model. However, while flexibility in the project execution is certainly necessary for the successful execution of most transformation projects, it does not necessarily warrant a complete lack of risk-sharing (eg, by using a 100 per cent time and material price model). A more tailored approach is often needed, containing a mix of time and material work (for the least predictable workloads), target-pricing or risk-sharing and fixed-price components.

Traditional project challenges, such as routines for ensuring continuity of personnel, routines for allocating project responsibility from the vendor to the customer, sanctions for delays, the process of defining requirements for the end result, etc, are still highly relevant when business transformation leverages cloud.

Still, cloud services raise specific challenges pertaining to handling multivendor landscapes. SaaS vendors are known for invoking broad reservation on the basis of the ‘business model’. Scalability is typically invoked for broad waivers and responsibility carve-outs. Ensuring key contracting points such as scope, price, time and responsibility is equally important for transformation services which leverages different cloud stacks, as for traditional IT services.

The demand for digital transformation leveraging cloud services has dramatically increased over the past five years. Traditional industries continue to seek renewal by leveraging hyperscalable infrastructure, standard software and platforms from multinational vendors. Local integrators are maturing and increasingly offers standardised and proven service offerings. Anecdotally, we have witnessed greater willingness for vendors to assume responsibility for the customer’s achievement of transformation business cases. The direction of travel seems to be increasing maturity on the local cloud service market, catering the demand for customer specific adaptations and integrations to standardised cloud services.

5 In your experience, what are the typical points of contention in contract discussions and how are they best resolved?

The ‘usual suspects’ continue to be the most common points of contention in supplier or customer contract discussions, as much of the contract discussions often revolve around topics such as price, liability and remedies.

The shift towards increased standardisation of service offerings and contracts in connection with increased adoption of cloud-based solutions often creates less room for negotiations, for example with respect to the technical infrastructure of the service in question (eg, data centre localisation) and the degree to which the suppliers are able or willing to accept liability for third-party components of the services.

The increased standardisation is also generally reflected in the sanctions and remedies suppliers are willing to offer (increasingly restricted to service credit regimes) and the liability limitations they are willing to accept. The topic of liability under data processing agreements has, in particular, become a recurring point of contention in contract discussions, as many customer organisations demand uncapped liability that the suppliers are unwilling to accept.

From the supplier’s side, a recurring theme is that these considerations are often a reflection of risk factors underpinning the supplier’s pricing strategy, and a precondition for being able to offer the services in question at the quoted price point. Many Norwegian customers, however, are accustomed to a more broad and general scope of the supplier’s responsibilities, and the customer’s access to remedies.

This creates a tension between the interests of the supplier and customer side of the negotiations that is not always easy to reconcile.

However, most customer and supplier organisations are reasonable, and willing to make concessions in the interest of supporting a good cooperative relationship going forward. Our experience is that most points of contention may be resolved by addressing the concerns underlying each party’s positions through pinpointed contractual measures.

As an example, customer organisations are often understanding of the fact that modern digital solutions are multifaceted, and often reliant on contributions and services from third parties over which the supplier will have little actual control (eg, cloud platform providers). They will therefore often accept that the supplier is unwilling to insure the customer with respect to deficiencies in such third-party components or services by accepting liability beyond what the supplier may enforce itself towards the third-party provider in question. Conversely, suppliers may often be willing to accommodate a more expansive sanctions regime with respect to service elements where there are fewer third-party dependencies (albeit often subject to adjustments in the contract price reflecting the supplier’s perceived risk increase).

A final and more general source of some contention in contract discussions, are disagreements concerning the contract format, structure and language itself. Many Norwegian organisations are now contracting using contractual templates originating from, or inspired by contractual traditions in, other jurisdictions. Norwegian contracts have traditionally been more general and simpler in construction and language, relying on background law to safeguard the interests of the parties under circumstances which are not explicitly regulated in the contract. Internationally inspired, and more comprehensive, contracts may therefore be met with some scepticism and require some additional rounds of negotiations before both parties are comfortable and content with the final product. This latter point should, however, not be exaggerated.

6 How do your jurisdiction’s cybersecurity laws affect organisations on their digital transformation journey?

As Norway does not currently have any cybersecurity laws that apply generally, most Norwegian organisations’ digital transformations are not affected by statutory cybersecurity requirements. However, certain exceptions do apply within specific industries and business sectors, as discussed above.

Both generally, and for those organisations subject to sector-specific regulations, we are increasingly seeing a trend towards using standardised tools and certifications to substantiate cybersecurity credentials and demonstrate contractual or statutory cybersecurity requirements.

7 How do your jurisdiction’s data protection laws affect organisations as they undergo digital transformation?

Norway has implemented the GDPR, and the Norwegian Data Protection Authority have generally aligned its application of the GDPR with the European Data Protection Board (EDPB) and the supervisory authorities in the other Nordic countries. Norwegian data protection law is therefore generally aligned with, and poses few additional restrictions compared to, the data protection law in other European countries.

With respect to data localisation requirements and export restrictions, there are some national laws that may affect organisations’ ability to leverage a decentralised technical infrastructure (eg, cloud solutions) which involve transmitting, storing and processing data outside of Norway.

While Norway has comparatively few data localisation requirements and restrictions, there are some laws and regulations that require local data storage. These restrictions are primarily intended to protect the tax authority’s access to certain financial information. The Bookkeeping Act and bookkeeping regulations include requirements for local storage with respect to accounting materials and electronic cash register journals as the main rule, although exceptions do apply. There is also a requirement to store tax documentation within Norway for a period of five years pursuant to the tax payment regulations.

One other, and more general data localisation requirement follows from the Norwegian Archiving Act, which requires that all public bodies must store data subject to their archiving duties within Norway. As with the accounting materials, exceptions may be made in certain circumstances. Private organisations are not subject to this requirement.

We should note that there is some uncertainty with respect to whether the data localisation requirements and restrictions that Norway have will remain in place, and in what form. Norway implements EU directives and regulations through the EEA, and is assessing the need to amend the data localisation provisions we do have in order to implement regulation 2018/1807 on a framework for the free flow of non-personal data in the European Union (FFD). The provisions discussed above in this part are among those being reviewed as a part of this process.

8 What do organisations in your jurisdiction need to do from a legal standpoint to move software development from (traditional) Waterfall through Agile (continuous improvement) to DevOps (continuous delivery)?

An organisation moving from Waterfall development, employing a vendor to provide a fixed outcome against a fixed price, through Agile development and DevOps needs to rethink and recalibrate its entire risk approach.

While we rarely see true Waterfall development projects these days, most organisations in Norway run multiple Agile projects, employing experts from specialised vendors. However, while vendors employ Agile development models, many customers still expect the cost predictability offered by traditional Waterfall models. An unspecified scope coupled with a fixed price or risk sharing price model often creates conflicting interests between the vendor and the customer and tension in these projects, and we have seen a quite substantial increase in litigations over failed Agile projects the last few years due to this phenomenon.

Businesses embracing true Agile and DevOps development models with incremental development, prototyping and frequent change (and frequent deployment in DevOps) to accommodate frequently shifting business need to reconsider their mindset and rather think of these as in-house activities, despite engaging external expertise. These businesses may use Agile and DevOps internally already, but we often see that as soon as they need external experts, they view the relationship as a vendor−customer relationship, using traditional IT contract templates. However, if they contract these experts under augmentation contracts, they will probably get most value for their money.

With respect to DevOps in particular, we are seeing a shift from more traditional application management contracts distinguishing between application operation services, application maintenance services and application development service to contracts combining these service elements and changing service management service descriptions and service level measurements.

9 What constitutes effective governance and best practice for digital transformation in your jurisdiction?

Unfortunately, traditional technology sourcing models and contracts still seem to be most frequently used in digital transformation projects in our jurisdiction. While this seems to be the prevailing practice, it is in our view not necessarily the best practice.

In our view, digital transformation projects are less about technology than people and business processes. Any digital transformation process must take this into consideration. When a business runs a digital transformation project it is of key importance that the project staff understand the business, its people and associated opportunities and challenges. In order to cater for this understanding, the digital transformation project must be governed in a manner where this insight is obtained, processed and the digital transformation solutions are validated with key stakeholders in the business. This applies for any digital transformation initiative, whether it is being run by internal or external project members.

When employing an external vendor to participate in, run, or manage the digital transformation initiative, effective governance also requires identification of potential diverging interests between the vendor and the customer and addressing and managing these in the relationship. These diverging interests almost invariably revolve around the topic of commercial risk. Using the contract negotiation process to identify, address and manage these diverging interests, is in our experience the most effective way to manage this. In our experience, capturing governance mechanisms suited to the specific relationship in the contract, including the proper commercial model, is the key to success.

The Inside Track

What aspects of and trends in digital transformation do you find most interesting and why?

Over the past few years, we have seen an increasing number of clients resorting to a hybrid approach, combining public cloud, single tenant and more traditional infrastructure solutions to achieve a balance of accessibility, simplicity, compliance and control. This, in particular, applies to larger organisations with existing, complex digital infrastructures, and clients in regulated business sectors such as banking and finance. This trend highlights that more ‘traditional’ and mature solutions still have a role to play in digital transformation projects.

What challenges have you faced as a practitioner in this area and how have you navigated them?

In negotiations, particularly involving larger organisations, certain fixed contracting principles and policies may often result in the parties assuming somewhat confrontational positions. Approaching these negotiations with a degree of pragmatism is often required in order to help the client make progress in difficult negotiations. This, in turn, requires a clear view of the client’s goals in order to practice a correct prioritisation of positions and ensuring that positions achieved in one area do not come at the cost of concessions that are ultimately detrimental to other important interests of the client.

What do you see as the essential qualities and skill sets of an adviser in this area?

The most essential skillset is being able to identify the key interests of the client and understanding its business objectives. This enables devising a tailored legal strategy with a clear prioritisation of positions and a focus on ensuring that these interests are protected.

Having experience in assisting both supplier and customer organisations in digital transformation projects, coupled with a proactive approach, is often essential in guiding the client in the process of understanding the counterparty’s position and prioritising one’s own.

Additionally, it is important that the adviser is able to keep in mind that the commercial potential of the transformation will always be most important to the client and that the advisory services should therefore always focus on achieving the contractual and operational results necessary to realise these benefits.