BRC A.I CyberSecurity Scoring
19/02/2026
Access Monitoring Plan
Access Monitoring Plan
No incidents recorded for British Red Cross in 2026.
No incidents recorded for British Red Cross in 2026.
No incidents recorded for British Red Cross in 2026.
Organization supported by Brazilain industries in order to contribute for industrial entreprises competitiveness and susitainability through the promotion of quality of life of industrial workers. SESI offers services on Education, Health, Leisure and Social Responsibility areas. SESI National Department define and implement strategies, policies and guidelines, leading the "SESI System" and its 27 Regional Departments.
Latest updates, reports, and threat intel affecting the global network.
Andrea Farrés Jiménez. Andrea Farrés Jiménez is a British Red Cross Research Fellow on the joint British Red Cross/International Committee...
How the ICRC's 2005 study on customary IHL clarified gaps left by the treaties, and helped to strengthen the practical application of IHL.
The International Committee of the Red Cross will reduce its 2026 budget by nearly a fifth to 1.8 billion Swiss francs ($2.2 billion) and...
Exclusive: More than 6000 children will be unable to reunite with their loved ones after government paused major route for refugees to come...
The British Red Cross Christmas market returns to London's Guildhall on December 8–9, offering festive shopping, entertainment,...
In December 2024, Prism Infosec were appointed on behalf of the Department for Science, Innovation and Technology ( DSIT ) to conduct...
HCSS is pleased to announce that Charlotte Lindsey has joined us a non-resident Subject Matter Expert! Her work focuses on the impact,...
The institutions have provided funds to youths in Kirinyaga Red Cross toward raising fruit seedlings for passion and Hass avocados to mitigate global warming.
Charities are introducing four-day working weeks despite concerns it could lower standards and raise costs for taxpayers. The British Red...
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.
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.
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.
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.
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.
curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'
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.
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.