What is the official website of Nordisk Film Kino ?

The official website of Nordisk Film Kino is http://www.nfkino.no.

What is Nordisk Film Kino's cybersecurity risk score?

Nordisk Film Kino has an AI-generated cybersecurity risk score of 821 out of 1000, indicating a Good security posture according to Rankiteo's assessment.

How many security incidents has Nordisk Film Kino experienced?

According to Rankiteo, Nordisk Film Kino currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Has Nordisk Film Kino been affected by any supply chain cyber incidents ?

According to Rankiteo, Nordisk Film Kino has not been affected by any supply chain cyber incidents, and no incident IDs are currently listed for the organization.

Does Nordisk Film Kino have SOC 2 Type 1 certification ?

According to Rankiteo, Nordisk Film Kino is not certified under SOC 2 Type 1.

Does Nordisk Film Kino have SOC 2 Type 2 certification ?

According to Rankiteo, Nordisk Film Kino does not hold a SOC 2 Type 2 certification.

Does Nordisk Film Kino comply with GDPR ?

According to Rankiteo, Nordisk Film Kino is not listed as GDPR compliant.

Does Nordisk Film Kino have PCI DSS certification ?

According to Rankiteo, Nordisk Film Kino does not currently maintain PCI DSS compliance.

Does Nordisk Film Kino comply with HIPAA ?

According to Rankiteo, Nordisk Film Kino is not compliant with HIPAA regulations.

Does Nordisk Film Kino have ISO 27001 certification ?

According to Rankiteo,Nordisk Film Kino is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Which industry does Nordisk Film Kino operate in ?

Nordisk Film Kino operates primarily in the Movies, Videos, and Sound industry.

How many employees does Nordisk Film Kino have ?

Nordisk Film Kino employs approximately 83 people worldwide.

Does Nordisk Film Kino own any subsidiaries ?

Nordisk Film Kino presently has no subsidiaries across any sectors.

How many LinkedIn followers does Nordisk Film Kino have ?

Nordisk Film Kino's official LinkedIn profile has approximately followers.

Does Nordisk Film Kino have a Crunchbase profile ?

No, Nordisk Film Kino does not have a profile on Crunchbase.

Does Nordisk Film Kino have a LinkedIn profile ?

Yes, Nordisk Film Kino maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/nordisk-film-kino.

How many cybersecurity incidents has Nordisk Film Kino experienced ?

As of July 17, 2026, Rankiteo reports that Nordisk Film Kino has not experienced any cybersecurity incidents.

How many peer or competitor companies does Nordisk Film Kino have ?

Nordisk Film Kino has an estimated 1,840 peer or competitor companies worldwide.

NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop

WindowsmacOSLinux

Download

Badge your company to reduce your risk score and your cyber insurance costs!

Link verified badges to your company page to build trust with insurers and customers.

Apply now and get your badge!

Internal validation & live display

Insurers and partners see a safer profile

Faster underwriting decisions

Trusted by insurers. Chosen by leaders.

Proud contributor to the Society of Actuaries.

NFK

Boost Score +25 with badge (5 left)

821

/1000

Good

846

/1000

Good

Nordisk Film Kino Vendor Cyber Rating & Cyber Score

nfkino.no

Add Your Compliance Badge

Nordisk Film Kino er Norges største kinokjede. Vi tar imot 3,2 millioner årlige besøkende til våre 21 kinoer i Oslo, Arendal, Asker, Askim, Drammen, Farsund, Halden, Horten, Hønefoss, Kristiansand, Kristiansund, Tønsberg, Verdal og Ålesund. I dag kan filmopplevelsen både starte og slutte online. Våre kinoer kan brukes til andre arrangementer enn film. Flere av våre saler har scener og kan brukes til konserter, kulturelle arrangementer. De kan også tilrettelegges og skreddersys for ulike events. Film er best på kino! Vi ses! Direktør for Nordisk Film Kino: Jannicke Haugen

NFK A.I CyberSecurity Scoring

Scoring History

NFK

Nordisk Film Kino CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

No data available

Loading…

A.I.

NFK Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Actual

Prediction

Incident Predictions locked

Access Monitoring Plan

A.I Risk Score Likelihood 3 - 6 - 9 months

Actual

Prediction A

Prediction B

Prediction C

Prediction D

A.I. Risk Score Predictions locked

Access Monitoring Plan

Loading…

Underwriter Stats for NFK

Incidents vs Movies, Videos, and Sound Industry Avg (This Year)

No incidents recorded for Nordisk Film Kino in 2026.

Incidents vs All-Companies Average (This Year)

No incidents recorded for Nordisk Film Kino in 2026.

Incident Types NFK vs Movies, Videos, and Sound Industry Avg (This Year)

No incidents recorded for Nordisk Film Kino in 2026.

Incident History - NFK (X = Date, Y = Severity)

Loading…

SUBSIDIARY

Nordisk Film Kino Subsidiaries

Parent Company

NFK

Movies, Videos, and Sound

Website: http://www.nfkino.no

Company Size: 83

No subsidiary data available for this company.

Loading…

Nordisk Film Kino Similar Companies

Loading…

NEWS

Nordisk Film Kino CyberSecurity News

Latest updates, reports, and threat intel affecting the global network.

Loading…

CVE

Latest

Global CVEs (Not Company-Specific)

CVE-2026-44453

SUMMARY

h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. Prior to commit 6b5370d, h2o is vulnerable to a Denial of Service attack when calling alloca under certain conditions. When serving static files, h2o builds the file path on stack, by calling alloca. The maximum size of the memory allocated using alloca can be as huge as ~600KB, which exceeds the default pthread stack size used by musl libc (128KB). If the amount of memory allocated by alloca exceeds the stack size, the h2o server crashes with a segmentation fault, while it tries to touch the guard page. This issue has been fixed by commit 6b5370d.

Published

Date2026-07-16

Updated

Date2026-07-16

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-44452

SUMMARY

h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. Prior to commit 8dc37cb, when h2o receives a ClientHello message over TLS or QUIC and it contains a zero-length SNI extension, the h2o server runs over the zero-length hostname while trying to copy the hostname, assuming that it is NULL-terminated. This is a potential denial-of-service attack vector in sense that it might trigger segmentation violation. This issue has been fixed by commit 8dc37cb.

Published

Date2026-07-16

Updated

Date2026-07-16

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

2.2

REFERENCES

CVE-2026-44436

SUMMARY

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, Quicly is vulnerable to a Denial of Service attack through connection state corruption. In QUIC Invariants, the maximum length of a Connection ID is 255 bytes, while QUIC version 1 further restricts the maximum to 20 bytes. Quicly implements QUIC version 1 and therefore its CID buffers are limited to 20 bytes. However, to be able to respond to unknown versions of QUIC, its packet decoder accepts Connection IDs of up to 255 bytes. As its CID buffers are merely 20 bytes long, Quicly must reject QUIC version 1 packets with Connection IDs longer than that. The command line tool bundled with Quicly has had that check, however the library itself lacked such enforcement. As a consequence, when used by applications that lack their own enforcement, the connection state becoming inconsistent to buffer overrun. Fortunately, the overflow stops within the allocated chunk of memory, but nevertheless, the bug leads to assertion failures. This issue has been fixed by commit 8b178e6.

Published

Date2026-07-16

Updated

Date2026-07-16

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-44435

SUMMARY

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 937d0e9, an assertion failure is raised when the total number of valid handshake messages received over a CRYPTO stream of a single packet number space exceeds 32KB, causing a Denial of Service. This issue has been fixed by commit 937d0e9.

Published

Date2026-07-16

Updated

Date2026-07-16

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-44434

SUMMARY

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is designed to withstand packet injection attacks, once the handshake is complete. Only packets that carry some secret patterns are considered as stateless resets. Quicly allows the peer to share up to 4 such patterns per connection. However, until now, it failed to determine which of the 4 slots that it uses to retain the secret patterns contains a valid entry. As the slots are zero-initialized, the failure meant that, unless the peer advertised 4 of such patterns, an all-zero pattern was treated as a stateless reset.In effect, this allowed an on-path attacker to reset QUIC connections governed by Quicly. This issue has been fixed by commit dccf5d4.

Published

Date2026-07-16

Updated

Date2026-07-16

RISK INFORMATION (Score: 5.3)

cvss3

Base Score: 5.3

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Impact Score

1.4

Exploitability

3.9

REFERENCES

Loading…

API

Access Data Using Our API

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'

Try It API Documentation Rapid

MEASURE

What Do We Measure ?

Incident

Finding

Grade

Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network SecurityIdentify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat IntelligenceLeverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Rankiteo

By Rankiteo

★ ★ ★ ★ ★

View on G2.com

Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.

View latest plans →View all security reports →

MILESTONEG

Users
Love Us

Loading…