
Government of the Netherlands
Government of the Netherlands



Government of the Netherlands

The Ministry of Health (MOH), by way of its objectives, policies and projects included in this strategy, seeks to accomplish a promising future vision; namely, delivering best-quality integrated and comprehensive healthcare services. Carrying health conditions or health status of Saudi inhabitants to the best and highest possible level, in terms of justice and equality in providing healthcare, and in terms of effectiveness and the possibility of incurring the financial burden of the treatment and healthcare. In doing so, the MOH takes as its target meeting citizens’ aspirations in this regard, by providing them with high-quality general and specialized health services, and covering all the population with these services. Creating a sole and exclusive entity to formulate health policies including health insurance services, etc. (such as operating the recently established Health Services Council.) Adopting a public and national health strategy which focuses of the main morbidity burdens; including non-communicable diseases, nutrition, reproductive health, smoking (tobacco-use), AIDS, traffic accidents, and injuries. The system must have an effective and fair method for estimating risks and benefits. Working to diversify sources of revenues to finance the system effectively. These sources must include also public revenues and insurance premiums, in addition to the equally allocated costs and taxes.
Security & Compliance Standards Overview












No incidents recorded for Government of the Netherlands in 2026.
No incidents recorded for Ministry of Health Saudi Arabia in 2026.
Government of the Netherlands cyber incidents detection timeline including parent company and subsidiaries
Ministry of Health Saudi Arabia cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.
PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.
PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.