Stefan Pfeiffer
Sales

Introduction

October 1, 2026, is fast approaching, and this is a date you should mark on your calendar. On this day, the new Network and Information Systems Security Act (NISG 2026) will take effect in Austria. However, this is not just another IT regulation, but a fundamental realignment of responsibilities for cybersecurity.

The biggest hurdle? Around 4.000 Austrian companies are directly affected, but many are still unsure how they are even supposed to meet these rather far-reaching requirements

This guide explains the core requirements of NIS2-Directive and highlights the often-overlooked but crucial role that professional license management plays in connecting NIS2 in Austria to ensure true compliance.

The Basics: What Does the NIS2 Directive Mean for Businesses in Austria?

Simply put, NIS2 is an EU-wide directive designed to strengthen cybersecurity in 18 critical sectors across Europe. In Austria, this directive is implemented by the NISG 2026 (Network and Information System Security Act 2026), which will apply to all affected companies starting October 1, 2026.

So who exactly is affected? Mainly medium-sized and large companies in the defined sectors. And that’s a huge jump: While the old NISG 2018 affected only about 100 companies, the number has now risen to around 4.000. Incidentally, all companies falling under this scope must register by December 31, 2026.

The directive distinguishes between “essential” and “important” facilities. The classification depends on the size of the company and the criticality of the sector. The main difference lies in the type of oversight (proactive for essential entities, reactive for important ones) and, of course, in the severity of the penalties for noncompliance.

Ein Vergleich verdeutlicht die Änderungen:

The Core Requirements of the NIS2 Directive

The NIS2 Directive is not purely an IT issue that can simply be passed on to the IT department. It touches on the very core of corporate risk management and places direct responsibility on senior management. Let’s take a closer look at the three most important pillars.

Cybersecurity Incident Response

NIS2 requires a comprehensive “all-hazards approach.” This means looking beyond the scope of traditional IT security. According to the overview provided by the Austrian Chamber of Commerce (WKO) , companies must implement a wide range of measures, including:

Strict Reporting Requirements for Security Incidents

When a serious security incident occurs, the clock starts ticking. NIS2 mandates a multi-stage reporting process to the responsible CSIRT (Computer Security Incident Response Team), such as CERT.at: Within 24 hours: An initial early warning must be issued. In many cases, it is sufficient to report a suspicion of an illegal act. Within 72 hours: The report must now be more detailed. An initial assessment of the severity, the impact, and so-called indicators of compromise is required. No later than one month after the report: A final report must be submitted. It must include a detailed description of the incident, an analysis of the causes, and the corrective measures taken.

This tight schedule puts enormous pressure on internal processes and makes a well-thought-out and, above all, proven contingency plan essential.

Personal Liability of Management

A key change is the introduction of personal liability for management bodies. Managing directors and board members must not only rubber-stamp and approve cybersecurity measures but also actively monitor their implementation, and they are personally liable for doing so .

What does this mean exactly? Not only does the company face substantial fines, but management can also be held personally accountable and, in the worst-case scenario, even be temporarily barred from holding executive positions. To fulfill this responsibility, managing directors and board members are even required to participate in specialized cybersecurity training.

The Critical Connection: License Management and NIS2

What does all this have to do with license management? More than you might think at first glance. The key point is this: You can only protect what you know, and you can only be accountable for what is documented.

A Comprehensive Software Inventory as a Foundation

One of the most fundamental requirements for effective risk management under NIS2 is knowing every single piece of software running on the network. Without a complete inventory, measures such as vulnerability management or access control are practically impossible.

This is where the major problem of shadow IT comes into play: unauthorized software or SaaS subscriptions that departments acquire without the IT department’s knowledge. These uncontrolled applications create massive security gaps and compliance risks, thereby undermining the principles of NIS2 at their core.

Professional Software Asset Management (SAM) is the only reliable way to create and maintain a complete and accurate inventory of all IT assets. It is the foundation of any serious cybersecurity strategy. Independent specialists such as LYYNX offer precisely this fundamental transparency as a managed service through their License Management Service (LMS), thereby laying the groundwork for a successful NIS2 implementation.

Vulnerability Management and Supply Chain Security

Once you have a complete software inventory, you can use it directly for vulnerability management. You can track versions, identify outdated and unpatched applications, and thereby meet a key technical requirement of NIS2.

At the same time, software vendors are a key part of the supply chain. NIS2 requires that the risks posed by these vendors be actively managed. Proper license management inherently involves the administration of contracts, usage rights, and vendor relationships, which directly contributes to the required supply chain security.

Quote from Lambert Huber: “A well-managed license inventory not only ensures compliance with vendors but also serves as crucial evidence for NIS2 audits that you have control over your software landscape.”

Audit Readiness and Traceability

Compliance with NIS2 is verified by the competent authority, the new Federal Office for Cybersecurity . In the event of an audit, you must be able to prove that you have done your due diligence.

A well-documented SAM or LMS process provides exactly this evidence. Reports on the software inventory, patch status, or usage data are crucial for demonstrating compliance. An independent partner like LYYNX Consulting helps you prepare all supporting documentation properly and ensure data quality. This makes your company “audit-ready” not only for software audits but also for inspections by NIS2 authorities.

The path to NIS2 compliance may seem complex, but there are many resources available to shed light on the process. To better understand the regulatory requirements and practical steps for businesses, the following video offers a helpful overview of current challenges and solutions in the area of compliance.

This video provides an overview of the growing regulatory requirements, such as DORA, the AI Act, and NIS2, and shows how companies can prepare for them.

NIS2 as an Opportunity for a Secure and Efficient Future

Yes, NIS2 is a legal requirement with severe penalties. But it is also a huge opportunity for Austrian companies to finally gain full control over their IT, drastically reduce security risks, and optimize costs at the same time.

Effective software license management is not merely a side task but a central pillar of successful NIS2 compliance. Companies that act now will not only avoid penalties but also build a more resilient and competitive organization. They’ll turn a regulatory obligation into a strategic advantage.

The regulatory landscape is complex, but you don’t have to navigate it alone. If you’d like to know how your current license management measures up to NIS2 requirements, schedule a no-obligation consultation with us—the vendor-neutral experts at LYYNX Consulting.

We’ll show you how to achieve clarity, security, and compliance.

Frequently Asked Questions

What is the biggest challenge in implementing NIS2 in Austria?

The biggest challenge is often the lack of transparency across the entire IT landscape. Without a complete and up-to-date software inventory, it is impossible to assess risks, manage vulnerabilities, or ensure supply chain security—all of which are core requirements of NIS2.

Who is responsible for NIS2 within a company in Austria?

Senior management bears personal and ultimate responsibility. NIS2 requires managing directors and board members to actively oversee the implementation of cybersecurity measures. However, operational implementation is a cross-departmental task involving IT, procurement, legal, and management.

How does an external service provider like LYYNX help with NIS2 compliance?

An independent specialist like LYYNX Consulting establishes the data foundation for NIS2 compliance. Through a managed service such as the License Management Service (LMS), a comprehensive software inventory is created and continuously monitored. This provides the necessary evidence for audits and helps proactively manage risks.

When must the NIS2 requirements be met in Austria?

The relevant law (NISG 2026) takes effect on October 1, 2026. Affected companies must register with the competent authority by December 31, 2026, and comply with the requirements as of the effective date.

What penalties apply for non-compliance with NIS2 regulations?

The penalties are substantial and tiered. For “critical” entities, they can amount to up to 10 million Euros or 2% of global annual revenue. For “important” entities, the fines are up to 7 million Euros or 1.4% of revenue. In addition, senior management is personally liable.

Is NIS2 just an issue for the IT department?

No, absolutely not. While the IT department plays a central role in the technical implementation, NIS2 is a strategic issue for the entire company. Due to personal liability and the far-reaching requirements for risk management, it is an issue that falls directly under the purview of senior management.

Start now with a no-obligation initial consultation – and gain clarity on the actual optimization potential of your license portfolio..

Get the latest news delivered straight to your inbox – subscribe to our newsletter now!

Stefan Pfeiffer
Sales

Uwe Franke
Consultant

Licensing costs keep rising - how can you avoid them?

Microsoft has just announced that prices will rise again in the summer of 2026. The announcement was made in a blog post.

In a nutshell—new AI security and management features, but higher prices!

Key new features:

Copilot Chat

It is already available for free, but is set to be further developed, improved, and expanded, particularly within Office apps such as Outlook, Word, Excel, and PowerPoint.

Most users don’t take advantage of all the features these applications offer – it’s possible that additional unused features will now be added.

Enhanced Security

Microsoft Defender for Office 365 Plan 1 is being integrated into M365E3 – previously, it was only available in the M365E5 Suite or M365E5 Defender Suite, or as a standalone plan.

It is enabled by default for ALL users in the tenant (according to Microsoft’s product terms, all users must be licensed!!!) – administrators must then ensure that only licensed users can benefit from this service.

More IT Tools

Intune Remote Help: is enabled at the tenant level and cannot be restricted.
If the manufacturer has access to the tenant, it can view the enabled services, which could result in additional charges.

This isn’t the first time Microsoft has raised prices – here’s a brief timeline…

Although the currency fluctuation would be about -10%, we’re satisfied with -7.4% in the eurozone – after all, we don’t want Microsoft to be struggling to survive and possibly start cutting back on investments in the cloud and AI. An adjustment would have been possible – or even necessary—as early as October 2025, but this delay will certainly satisfy the shareholders once again.

Case Study:
The customer has a Level D Enterprise Agreement (15,000 seats or more) with M365E3; some users utilize landline telephony and meeting rooms with Teams; some use Power BI Pro; and Dynamics 365 CRM is in use in the sales department.
Additional products such as Visio, Project, Exchange Online, or Copilot, as well as infrastructure products (e.g., Windows/SQL Server), are not included.
Increases in volume or upgrades to other products (e.g., from M365E3 to M365E5) are also not included.
A Level D customer certainly does not purchase at list price but receives a discount during contract negotiations; however, this discount has actually been decreasing in recent years, unless the customer purchases what Microsoft wants, in which case higher discounts are possible.

All features and services remain the same as in the previous contract.
The 3-year contract will cost 18.00% more – an additional € 3,394,864.80

Forecast for July 2026

Over the three contract periods (comparing Contract 1 to Contract 3), an increase of +6,559,833.60 € → a 42.60% increase.

In return, meeting room services (Teams Rooms) offer more features and enhanced security in M365E3. More IT tools and AI agents are included in the products and services.

…and we’re supposed to pay almost double for that?

Dear Microsoft, you have good products; they work, and people can get work done with them.
But perhaps you aren’t aware yet – there are companies that rely on other technologies or vendors for security and IT tools, for example, and there are also employees within those companies who don’t necessarily need or use AI features in the products.

Dear End Customers, how many more times can you go to the well before the jug breaks?
Prices are rising across the board – including software costs!
Without software, operations simply won’t function—carrier pigeons, clay tablets, and slide rules are a bit out of style.
What can you do to prevent software costs from rising even further?

Software costs can be effectively reduced on several levels – organizational, contractual, and technical.

In short:
Costs drop the most where transparency, clear processes, and active management come together. Often, just a few targeted measures are enough to achieve noticeable savings.

Support from external experts during contract negotiations can also save a great deal of money—these experts may have already negotiated or assisted with other contracts with Microsoft and can bring their experience to bear in your negotiations.

These experts can also point out what to look out for regarding Microsoft licensing, as well as the potential impact of product suites on your compliance and any potential additional charges from the vendor (e.g., tenant activation that cannot be restricted).

You’ll typically recoup the costs of such a project during contract negotiations—without having to completely overhaul your services or infrastructure.

Start now with a no-obligation initial consultation – and gain clarity on the actual optimization potential of your license portfolio..

Get the latest news delivered straight to your inbox – subscribe to our newsletter now!

Uwe Franke
Consultant

Lambert Huber
CEO

What’s what?

IT Asset Management? Software Asset Management? Or just “something to do with inventory”? Put simply, asset management refers to the management of “things that represent value” – more specifically, those that incur or have incurred costs. These can include cars, office furniture, machinery, or even computers and software.

Just as an asset register is important for cars and real estate, keeping detailed records of IT assets in a company is also sensible – if not required.

The Big Picture – Asset Management

1. IT Asset Management (ITAM)

ITAM refers to the management of all IT assets, including hardware, software, and the relatively new discipline of services (more specifically, SaaS or compute resources).
ITAM is described in great detail, particularly in the ITIL V4 framework, and provides numerous best practices. Hardware Asset Management (HAM) and Software Asset Management (SAM) are subdisciplines of ITAM.

ITAM therefore encompasses both hardware and software asset management.

2. Hardware Asset Management (HAM)

HAM involves the management of all hardware resources within the company. This essentially includes:

There are no explicit standards for hardware asset management. However, the processes described above are addressed in control frameworks such as COBIT, ITIL, etc.

One can also refer to the ISO 55000 series (ISO 55001, ISO 55002), which describes asset management in general terms.

3. Software Asset Management (SAM)

SAM is also a component of ITAM and focuses on the management of software assets. In a narrower sense, it involves the inventory and documentation of paid software, sometimes referred to as proprietary software.
Free software (e.g., open source) does not strictly fall under the scope of SAM. However, in some cases, it may make sense to manage it as well.
The discipline of SAM is described in great detail in the ISO 19770 series. The standard is now in its fourth iteration.

4. License Management / Compliance Management

Within software asset management processes, the license management / compliance management process reflects the comparison between assets in use and asset entitlements. This is often referred to as a “license balance sheet,” although this term is not entirely comparable to an accounting balance sheet.

The following terms are used in license management:

EDP – Effective Deployment Position

means “What is in use – for what is a license required or would be required.”

ELP - Effective License Position

means “Which licenses or license entitlements are permitted to be used.”

Comparing these two positions yields the license balance per asset.
The figure can be negative (under-licensing), positive (over-licensing), or – ideally – zero.

How does asset management differ from other IT management disciplines?

Asset management is primarily concerned with the management of assets. It therefore always involves costs, investments, and accounting issues.
Nevertheless, asset management also relies on technical data. This is where things that have nothing to do with asset management per se are often conflated.
We repeatedly encounter misunderstandings about which discipline should be used for what. Technical or organizational issues are often conflated with the business-oriented discipline of ITAM.

Here are a few typical confusions – I call them “false flags” – that sound a bit like ITAM but actually have little to do with it.

False Flag 1 – IT Service Management (ITSM)

Service management involves defining a service and operating it reliably. When managing a service, it is important to define all components involved, identify bottlenecks, and develop backup and scaling strategies.

Distinction from ITAM
In the ITAM process, the relationships between assets (service map) are irrelevant; only the associated risk and costs matter. Conversely, in the ITSM process, the cost of a service component (which may even be free) is irrelevant; only its availability matters.

False Flag 2 – IT Configuration Management

IT Configuration Management can be viewed as an “upstream” discipline to Service Management. CM organizes all components of an IT infrastructure into Configuration Items (CIs), which can then be grouped together to form a service.
The CIs are managed in a Configuration Management Database (CMDB) and made available to other disciplines (e.g., the ITAM process).

Distinction from ITAM
Configuration Management can, under certain circumstances, be managed in a very static manner, even involving purely manually maintained data records. In many cases, this actually improves data quality. ITAM, by contrast, always requires up-to-date data on end devices. Incidentally, a license is, by definition, not a Configuration Item (CI), although it is sometimes treated as such – due to the absence of ITAM.

False Flag 3 – Endpoint Management

Endpoint management is a purely technical discipline and serves primarily to deploy software to computers and servers, configure settings (e.g., policies), and install updates. The goal of endpoint management is to ensure that the configuration and operational security of clients and servers are always up to date.

Distinction from ITAM
Like ITAM, Endpoint Management requires up-to-date data on all computers and servers – in other words, a clean inventory. In this regard, the two disciplines can even complement each other. The main difference, however, is that Endpoint Management actively makes changes, whereas ITAM only accesses the systems in read-only mode. Furthermore, licenses (i.e., usage rights) are irrelevant to Endpoint Management.

I have singled out these disciplines because they are particularly often confused with ITAM-related initiatives.

SAM Tools – Are They Really Necessary?

This question is as old as the discipline itself. Let me clear up a few misconceptions here as well. SAM purists often say that an Excel spreadsheet can handle everything.
A SAM tool makes sense when the complexity of the IT environment exceeds a certain threshold. This could be the number of computers, contracts, employees, software products in use, or the number of changes to any of these parameters.
It’s difficult to give a definitive answer here, but it’s safe to assume that an environment with more than 500 computers is difficult to manage, and one with 1,000 computers is nearly impossible to manage without an ITAM tool.

ITAM: The Next Level – FinOps – What Is It, Anyway?

I’ll definitely be writing one or more blog posts on this topic. The term is currently being used in so many different contexts that it’s getting hard to keep track of it all.

Start now with a no-obligation initial consultation – and gain clarity on the actual optimization potential of your license portfolio..

Get the latest news delivered straight to your inbox – subscribe to our newsletter now!

Lambert Huber
CEO

Stefan Pfeiffer
Sales

Why Software Asset Management (SAM) and license management are indispensable for modern IT departments, and how companies can take advantage of hidden savings on license costs.

In many companies, software landscapes are growing faster than they can be managed. New applications are introduced, old licenses aren’t consistently decommissioned – and it’s not uncommon to lack a complete overview of costs, usage, and contractual obligations.
Software Asset Management (SAM) addresses this very issue: It creates transparency across the entire software lifecycle – from needs analysis through procurement and usage to end-of-life. When implemented correctly, SAM helps avoid unnecessary licensing costs, minimize audit risks, and make IT and license management processes significantly more efficient.

In this article, you’ll learn exactly what Software Asset Management is, how it differs from traditional license management – and why SAM is now an essential component of professional IT strategies and procurement processes.

Definition:
What is Software Asset Management (SAM) and License Management?

Software Asset Management (SAM) refers to the systematic process of managing and optimizing all software assets within a company – throughout their entire lifecycle. The goal is to maintain a complete, legally compliant, and cost-effective overview of the software products in use, licenses, usage, and contracts at all times.

Ideally, SAM begins with a needs analysis, accompanies procurement and implementation, monitors actual usage, and ends with the decommissioning or return of licenses. In doing so, it supports both operational processes and strategic decisions in IT, procurement, and controlling.

A common misconception is that a CMDB (Configuration Management Database) is sufficient to fully cover SAM. While a CMDB provides valuable information about software installed on end devices, it does not automatically capture license agreements, usage rights, contractual terms, or economic aspects. However, these commercial and licensing dimensions are crucial for managing software in a cost-effective and legally compliant manner.

SAM combines both perspectives but goes beyond them: It integrates legal, business, and technical information into a holistic management tool.

Given growing IT complexity, increased cloud usage, and ever more frequent vendor audits, SAM is no longer purely an IT issue – it is now a company-wide responsibility. Those who fail to establish clarity in this area risk not only unnecessary costs but also legal and security-related consequences.

What Does Software Asset Management (SAM) entail?

SAM is often equated with license management – but in reality, it is a holistic process that goes far beyond Excel spreadsheets. To reap the full benefits, you need to keep the entire software lifecycle in view. The goal is to ensure that every phase is managed in a controlled and traceable manner – from the initial need for the software to its removal from the company.

Managing these phases efficiently requires more than manual processes – this is where specialized SAM tools come into play.

Which systems and tools support SAM?

Efficient software asset management is virtually impossible without appropriate technical support – especially in medium-sized and large IT environments with a multitude of applications, platforms, and licensing models. Manual data collection quickly reaches its limits in such environments. To implement SAM effectively, specialized systems are needed that reliably consolidate technical, business, and licensing information.

Only by linking this information can a complete picture emerge, one that allows software to be not only technically inventoried but also managed correctly from both a business and legal perspective. Modern SAM tools often integrate these functions into a central platform—ideally with automated reconciliations, reports, and recommendations for action.

Manual vs. Automated License Management

In many companies, software asset management begins with good intentions – but with limited resources. License documentation is collected, Excel spreadsheets are maintained, and installations are documented manually or compiled from existing IT systems. The data often comes from various sources: procurement systems, inventory lists, Active Directory, SCCM, or CMDBs.

This form of “manual SAM” is thus based on scattered information that must be time-consuming to consolidate, maintain, and interpret.
What initially seems manageable quickly becomes a problem as the company grows.

Roles and Responsibilities in the SAM Process

Software Asset Management is not a single task – it is a cross-functional process that works only when responsibilities are clearly defined. Contrary to popular belief, responsibility for SAM does not lie solely with the IT department. For SAM to function effectively over the long term, multiple departments must work closely together.

Why SAM Is Not Just an IT Issue

While SAM does involve the IT infrastructure, it is far more than a technical inventory. It is about business management, risk mitigation, and strategic planning. These goals can hardly be achieved without the involvement of procurement, controlling, and legal departments.

That is why it is advisable to define the roles in the SAM process in a structured manner – for example, in a clear responsibility matrix (such as the RACI model) that specifies who is responsible for which tasks, who is involved, and who needs to be informed.

Such a structured approach lays the foundation for a functioning SAM – and creates the basis for a transparent and audit-ready approach to software management.
The next question is: Why is this effort actually worthwhile – and what concrete benefits does SAM bring to the company?

Why Software License Management Is Essential Today (License Compliance & Cost Control)

Software Asset Management (SAM) not only provides a better overview of licenses – it creates measurable added value in several areas. In an increasingly complex IT world with diverse licensing models, hybrid system landscapes, and growing audit pressure, SAM is no longer just a “nice-to-have” for many companies, but a decisive competitive factor.

Cost Control and Savings Potential

Many companies pay for licenses they don’t even actively use. SAM helps identify this phenomenon – also known as “shelfware.” Unused software can be decommissioned or reused (reharvesting) instead of purchasing new licenses. This allows budgets to be used more efficiently – without restricting users.

Audit Protection, License Compliance, and Minimizing License Risks

Vendor audits are no longer uncommon – and they often happen on short notice. Without SAM, you lack the data needed to provide structured and complete proof of licensing compliance. This can lead to high back payments, contractual penalties, or even legal consequences. An effective SAM significantly reduces this risk and strengthens your negotiating position with vendors.

Contribution to IT Security

Unauthorized software installations, known as “shadow IT,” pose a security risk. SAM helps identify and consistently remove such installations. At the same time, it enables better monitoring of security-related updates and license terms (e.g., for end-of-life products).

Sustainability and Resource Efficiency

Licenses are digital resources – and like any resource, they should be used sparingly and responsibly. Through targeted reuse and needs-based license allocation, SAM helps reduce IT’s environmental footprint – an aspect that is becoming increasingly important in the context of ESG initiatives and corporate sustainability reports.

The most common misconception: “We bought the license, so everything is fine.” However, actual usage often does not align with the agreed-upon licensing model. SAM reveals these discrepancies – and highlights where licenses have been overprovisioned, misallocated, or purchased unnecessarily. This opens up concrete opportunities for optimization that would not be apparent without SAM.

However, experience also shows that the path to a functioning SAM is not always easy. Poor data quality, unclear responsibilities, or a fragmented system landscape are among the most common stumbling blocks – especially when getting started. In the next section, you’ll learn what challenges companies typically face in this process and how you can specifically overcome them.

Common Challenges and How to Overcome Them

One of the most common hurdles is the lack of quality and consistency in the underlying data. License information, usage data, and contract details are often stored in different systems – ranging from Excel spreadsheets to procurement systems to CMDBs. This data is rarely complete, up-to-date, or linked together.

Poor Data Quality and a Fragmented Tool Landscape

One of the most common hurdles is the lack of quality and consistency in the underlying data. License information, usage data, and contract details are often stored in different systems – ranging from Excel spreadsheets to procurement systems to CMDBs. This data is rarely complete, up-to-date, or linked together.

Shadow IT and Unreported Installations

When employees install or use software without IT approval, it creates risks of license violations and security vulnerabilities. This so-called shadow IT is a reality in many companies – and often goes unnoticed as long as no technical controls are in place.

Complexity Due to Hybrid Infrastructures (On-Prem, SaaS, Cloud)

The transition to cloud-based applications and SaaS models significantly increases the complexity of license management. In addition to traditional on-premise licenses, subscriptions, usage rights, and service-level agreements must now also be taken into account – often with their own unique rules.

When companies identify these pitfalls early on and address them specifically, the result is far more than just an organized license inventory: it creates a robust foundation for transparency, efficiency, and security across the entire software management process.

And this is precisely where the true value of SAM lies – not just as a control tool, but as a strategic lever that enables companies to actively shape their IT landscape, better manage budgets, and minimize risks early on.
If you successfully navigate these pitfalls, SAM becomes a strategic lever – and that is exactly what we’ll explore in the next section.

License Management as a Strategic Competitive Advantage

Software Asset Management is far more than a technical administrative process. It is a company-wide management tool that connects IT, procurement, financial control, and compliance – and addresses precisely the areas where companies today face significant pressure to improve efficiency and reduce costs.

Conclusion

Companies that consistently implement license management not only save on license costs but also regain control, security, and decision-making freedom. Instead of reacting to audits or budget overruns, SAM enables you to lay the foundation for proactive action – regardless of vendor lock-in, infrastructure, or company size.

The sooner you start, the faster you’ll benefit:
from clear responsibilities, reliable data, and robust analyses.

Get started now – with a first, manageable step
Whether it’s tool selection, an inventory assessment, or a pilot project: We’ll help you implement SAM in your company in a structured and practical way.

Schedule a no-obligation initial consultation now and discover the true potential of your license portfolio.

Get the latest news delivered straight to your inbox – subscribe to our newsletter now!

Stefan Pfeiffer
Sales