Skip to main content

    Enterprise risk management

    Securitas’ process for enterprise risk management (ERM) is engrained in the business and seeks to identify, prioritize and manage the key risks to our business at all levels and in all parts of the business.


    Risksnurra_eng_0.png


    Securitas is exposed to various types of risks in its daily business. When providing security services, Securitas manages not only its own risks, but also risks on behalf of its clients. Minimizing the risk of a loss occurring, and thereby protecting our stakeholders, is an important objective. Securitas’ risks have been classified into three main categories: Operational risks, financial risks and strategic risks and opportunities.

    Operational risks

    Our own operational risk are the risks associated with our daily operations and the services we provide to our clients. The operational risks include a number of different areas such as the risk of not delivering services to our clients in line with contract obligations, that we as a company do not adhere to laws and regulations, the digital information security risk, the risk to our people etc.

    Financial risks

    Financial risks comprise risks within the financial area such as the cash-flow risk including that we manage the DSO (Days of Sales Outstanding) in an efficient manner, correct reporting of financial accounts, risks related to external financing needs, tax risk, currency exposure and so forth.

    To allow the divisions, countries and regions to focus fully on their operations, the management of certain risks (such as financing and currency) is centralized to the Group Treasury Centre, to the greatest possible extent.

    Strategic risks and opportunities

    Strategic risks and opportunities include that we to be a successful company need to ensure that we manage the strategic risks, that is to continuously follow, lead and adhere to industry trends, that we follow the macroeconomic situation, that we have continuous internal innovation and that we protect and develop the Securitas brand.

    All the risks in these categories can impact the Group’s financial performance and position if they are not managed in a structured way. Therefore, Securitas has developed its four-step process approach for managing enterprise risks. The four steps are described in further detail on the following pages:

    • Input and risk identification
    • Policy development
    • Risk management activities
    • Risk-based monitoring

    To support the ERM work, Securitas has implemented a web-based governance, risk and compliance (GRC) system that comprises all four steps in Securitas’ enterprise risk management process and gathers the ERM information in one database. The GRC system is used to streamline the ERM processes to further structure the processes and workflows and automates the processes, such as reports, with the aim to improve the overall quality of the ERM work and serves as a single point of information.

    Securitas' insurance and claims strategy is to "act as if uninsured". Read more about insurance as a risk management tool.

    Set my preferences

    You can decide how we use cookies on your device by adjusting the settings below. Click on “Accept all” if you accept all cookies. In this list of cookies you can choose the cookies that you would like to accept. If you do not accept the Google Analytics cookies to be stored, please leave the box unchecked. If you do not accept the Microsoft application insight cookies to be stored, please uncheck the box. All other cookies are considered as strictly necessary in order for you to be able to use and interact with the website and can therefore not be unselected. When you have made your choice, scroll down the list and then click on the “Confirm my choices” button in the bottom of the list. Please be aware that if you disable cookies you will not have access to the full functionality of the website.

    Click here to read our cookie policy
    • Name:
      _ga

      Used to distinguish users. A unique identifier associated with each user is sent with each hit in order to determine which traffic belongs to which user. This cookie enables the website's owner to track a visitor’s behavior and measure the website's performance. The main purpose of this cookie is to improve the website's performance.

      Name:
      _gat

      Used to throttle request rates for information on the website. This cookie does not store any user information. The main purpose of this cookie is to improve the website's performance.

      Name:
      _gid

      Used to distinguish users. This cookie enables the website's owner to track a visitor’s behavior and measure the website's performance. The main purpose of this cookie is to improve the website's performance.

    • Name:
      ai_session

      Speeds up page loading times and overrides any security restrictions that may be applied to a browser based on the IP address from which it comes.

      Name:
      ai_user

      Unique user identifier cookie for counting the number of users accessing an application over time.

    • Name:
      ARRAffinity

      Routes the request made through a web browser to the same machine in the DXC cloud environment. See ARRAffinity - Microsoft Azure. This cookie is deleted when you close your browser.

    • Name:
      __cfuid

      Speeds up page loading times and overrides any security restrictions that may be applied to a browser based on the IP address from which it comes.

    • Name:
      CookiesAccept

      Used to keep track of whether the user has accepted the cookie usage or not. This is not set unless the visitor has clicked on "Accept" in the cookie banner in the bottom of the website. The main purpose of this cookie is to improve the website's performance.

    • Name:
      EPiForm_{FormGuid}:{Username}

      Stores partial form submissions so that a visitor can continue with a form submission upon return. One cookie is created for each form and each logged in visitor. Stores the current submission status of the form (formGuid, submissionID, and if submission is finalized or not).

      Name:
      .EPiForm_BID

      Identifies the form submission made to the site when a visitor submits data via an Episerver form. Stores a GUID as the browser ID.

      Name:
      .EPiForm_VisitorIdentifier

      Identifies the form submission to the site when a visitor submits data to via an Episerver form. Stores a GUID which is the visitor identifier. Persistent (90 days from creation).

    • Name:
      EPI-MAR-<Content GUID>

      Records a visitor’s interaction with a running website optimization test, to ensure that a visitor has a consistent experience.

    • Name:
      ASP.NET_SessionId

      Used to keep track of a user navigating through the website. This is used to transfer information between pages and to store information that the user might reuse on different pages. The main purpose of this cookie is to improve the website's performance.

    Sorry, www.securitas.com does not support Internet Explorer. To enjoy our website, try using a newer browser like Chrome, Safari, Firefox, or Edge.