Skip to main content

Technical security

What IT and security staff need to approve and set up Placepoint: which TLS versions we accept, which hostnames and ports must be open, how sign-in and API access work, and how the data is encrypted. Roles, the data processing agreement and sub-processors are covered on Privacy and data processing.

This page covers Placepoint Fusion, Placepoint API, Placepoint AI, the help pages on docs.placepoint.no and the website placepoint.no.

HTTPS and TLS​

All traffic goes over HTTPS on port 443, encrypted with TLS.

  • TLS 1.2 is the lowest version. Connections using TLS 1.0 and TLS 1.1 are rejected.
  • TLS 1.3 is supported by all services, and we recommend it.
  • Requests on port 80 are redirected to HTTPS or rejected.
  • Fusion on app.placepoint.no, Placepoint API, the help pages and placepoint.no send Strict-Transport-Security (HSTS), so the browser only uses HTTPS.

Fusion and the help pages sit behind Azure Front Door, which terminates the TLS connection. Microsoft describes the TLS support there in the TLS policy for Azure Front Door.

Cipher suites​

All services support these four. All of them provide forward secrecy and authenticated encryption (AEAD).

TLS versionCipher suite
TLS 1.3TLS_AES_256_GCM_SHA384
TLS 1.3TLS_AES_128_GCM_SHA256
TLS 1.2TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Some of the services also accept older cipher suites for TLS 1.2, to support older clients. Set up integrations with the ones listed in the table.

Certificates​

The certificates are issued by public certificate authorities, have 2048-bit RSA keys and are renewed automatically. The services that run in Microsoft Azure use certificates from DigiCert, and Azure issues and renews them.

Do not lock a client to a specific certificate or intermediate certificate (certificate pinning). They are replaced without notice when renewed. Trust the root certificates that come with the operating system or browser.

Hostnames, ports and IP addresses​

The firewall must allow outbound HTTPS on TCP port 443 to the hostnames below. Real-time updates in Fusion go over WebSocket (wss) on the same port.

ServiceHostnameUsed for
Placepoint Fusionapp.placepoint.noThe web app and sign-in
backend.placepoint.noThe data the app shows
ws-v2.placepoint.noWebSocket
layers2.placepoint.noMap layers
assets.placepoint.noStatic files
Placepoint APIdata.placepoint.noAll endpoints in Placepoint API and token issuing
Placepoint AImcp.placepoint.no, mcp-dataset.placepoint.no, mcp-sweden.placepoint.noThe servers the AI tool connects to, see Installing Placepoint AI
Help pagesdocs.placepoint.noThe documentation and the developer portal
Websiteplacepoint.no, www.placepoint.noOur website

The simplest rule is to allow *.placepoint.no. The map in Fusion also fetches background maps and map layers directly from the providers' servers, including *.kartverket.no at Kartverket, *.geodataonline.no at Geodata and *.arcgis.com. Who provides what is listed on the provider pages. Icons and files in datasets are fetched from *.blob.core.windows.net. What else the browser must support is listed on System Requirements.

We have no fixed IP addresses. Fusion and the help pages sit behind Azure Front Door, where the addresses are shared with others and change without notice. Use hostnames in firewall rules, not IP addresses.

Sign-in and access​

Placepoint Fusion​

Placepoint API​

Placepoint AI​

Encryption and backups​

  • Fusion, Placepoint API and the data behind them are hosted in Microsoft Azure, in the Norway East region. See Where is the data stored? and the list of sub-processors.
  • Placepoint AI for Sweden, the server for Swedish property, runs on Amazon Web Services (AWS) in Ireland, with a certificate from Amazon.
  • The databases are encrypted at rest with transparent data encryption (TDE) and AES-256.
  • Files and datasets in Azure Storage are encrypted at rest with AES-256.
  • Microsoft manages the encryption keys, see encryption at rest in Azure. What this means under US law is described under CLOUD Act.
  • The databases are backed up automatically and can be restored to any point in time within the last seven days. In addition, we keep one backup a week for six months, one a month for two years and one a year for ten years. The backups are stored geo-redundantly, including in Norway West, which is the paired region of Norway East.
  • Microsoft's certifications and audit reports for Azure are available in Azure compliance and the Service Trust Portal. They apply to Azure as a platform.

Security questions​

If you have found a vulnerability, or your procurement team needs a completed security questionnaire, write to support@placepoint.no. The answers procurement teams ask for most often are in Short summary for supplier questionnaires. What happens in the event of a breach is described under What happens in a security breach? Financial institutions will find DORA on the same page.

See also​

These pages are generated automatically and may contain errors.This applies to screenshots and videos in particular. See About these help pages. Let us know through "Did you find what you were looking for?" at the bottom of the page, the chat at bottom right or support@placepoint.no.