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 sendStrict-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 version | Cipher suite |
|---|---|
| TLS 1.3 | TLS_AES_256_GCM_SHA384 |
| TLS 1.3 | TLS_AES_128_GCM_SHA256 |
| TLS 1.2 | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| TLS 1.2 | TLS_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.
| Service | Hostname | Used for |
|---|---|---|
| Placepoint Fusion | app.placepoint.no | The web app and sign-in |
backend.placepoint.no | The data the app shows | |
ws-v2.placepoint.no | WebSocket | |
layers2.placepoint.no | Map layers | |
assets.placepoint.no | Static files | |
| Placepoint API | data.placepoint.no | All endpoints in Placepoint API and token issuing |
| Placepoint AI | mcp.placepoint.no, mcp-dataset.placepoint.no, mcp-sweden.placepoint.no | The servers the AI tool connects to, see Installing Placepoint AI |
| Help pages | docs.placepoint.no | The documentation and the developer portal |
| Website | placepoint.no, www.placepoint.no | Our 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
- Each person has their own account and signs in with email and password.
- Sign-in uses Microsoft Entra External ID. Passwords are stored and checked by Microsoft, not in our databases.
- An account can only be signed in on one device at a time, and each sign-in is logged with its IP address. The service is to be used from the EU/EEA, see Access outside the EU/EEA.
- One-time code, two-factor, SSO and how long a sign-in lasts are covered on Account and sign-in.
- Your organisation's administrator adds and removes users, see User administration and Members.
- Personal data about private individuals is hidden until we have approved the need, see Access to personal data.
Placepoint API
- Placepoint API uses OAuth 2.0 client credentials. The client ID and secret are exchanged for a token at
https://data.placepoint.no/auth/token, see Authentication in the developer portal. - The token is sent as
Authorization: Beareron every call and usually lasts one hour. No keys appear in the URL. - Each endpoint requires a scope. Personal data also requires the
person:readscope and a signed data processing agreement. - The default limit is 120 calls per minute per token. Above the limit, the API responds with
429andRetry-After, see Rate limits and quotas. - How you get a client ID and secret is described under How do we get started with API access?
Placepoint AI
- The AI tool signs in with OAuth, using the same account as in Fusion. The servers have no users or keys of their own.
- Access follows the account, so the AI tool sees the same as the user sees in Fusion. Setup is described on Installing Placepoint AI, and who has access under Who has AI access?
- Personal data is not available through Placepoint AI.
- What we log is described under What does Placepoint log when an AI tool fetches data? Where the data goes is described under Placepoint AI and your own datasets.
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.



