From project to partner

A security system is often bought as a project. It is designed, installed and handed over, and then the supplier is done. But the system has to be operated, updated and documented for ten years or more. Over time many portfolios end up with several suppliers and different agreements. It also becomes unclear who has access to what.

This is supplier risk in practice. Who runs the system when the local installer stops? Where is the data, and who can process it? Who is responsible when a system nears the end of its life?

In this webinar we show what it means to have a partner and not just a supplier. It is about one party taking responsibility for security across the whole portfolio over time.

What we cover:

• How to map the supplier and third-party risk in your portfolio today
• What to require from a security supplier: data processing agreement, data storage and access management
• How operations, support and updates work after the project is delivered
• How to plan replacing old systems step by step, without doing everything at once
• What documentation the board and auditor need, and how to have it ready