If you are a medical device company dealing with growing cybersecurity regulations and patient data breaches — this project developed secure-by-design processor architectures tested specifically for medical applications. The SHARCS approach embeds security at the hardware level, meaning attackers cannot bypass protections through software exploits alone. With 8 consortium partners across 6 countries validating the approach, the results offer a tested blueprint for building inherently secure medical systems.
Built-In Cybersecurity for Medical, Cloud, and Automotive Systems From the Chip Up
Imagine your computer, car, or hospital equipment came with a lock built right into the hardware — not just software you install later. That's what SHARCS worked on: security baked into the chip itself, so attackers can't just bypass a software patch. The team tested this across three very different worlds — hospitals, cloud servers, and cars — to prove the approach works no matter the device. Think of it as moving from "adding an alarm system after the house is built" to "building the house with vault walls from day one."
What needed solving
Cyberattacks are growing more sophisticated, and software-only security keeps failing because it leaves the underlying hardware exposed. Companies in medical devices, cloud hosting, and automotive electronics face an arms race where every new software patch is just another layer attackers learn to bypass. The fundamental problem is that most systems were never designed to be secure from the ground up — security was bolted on afterward.
What was built
SHARCS produced 13 deliverables including secure processor designs, hardware-software security architectures, and demonstration applications for medical, cloud, and automotive domains. The project built a secure-by-design methodology that starts security at the chip level and extends it through every software layer to the end user.
Who needs this
Who can put this to work
If you are a cloud provider struggling to guarantee data isolation and end-to-end encryption for enterprise clients — SHARCS built and demonstrated secure hardware-software architectures specifically for cloud environments. The project addressed the reality that no cloud system is truly secure unless every layer, from processor to application, is hardened. This gives cloud operators a foundation to offer verifiably secure computing to regulated industries like finance and government.
If you are an automotive electronics supplier facing mounting pressure to secure connected vehicle systems against remote attacks — SHARCS demonstrated secure-by-design architectures validated for automotive applications. The project combined hardware-level security with software protections across 13 deliverables, tackling the specific challenge of securing legacy and new vehicle computing platforms. This work directly addresses the cybersecurity requirements emerging in UN R155 and ISO 21434 compliance.
Quick answers
What would it cost to implement SHARCS-type security in our products?
The project's EU contribution amount is not available in the dataset, so specific cost benchmarks cannot be provided. Implementation costs would depend on whether you adopt the secure processor designs, the software architecture patterns, or both. Contact the coordinator for licensing terms and integration cost estimates.
Can this scale to production volumes or is it lab-only?
SHARCS demonstrated its secure-by-design approach across 3 distinct application domains — medical, cloud, and automotive — which suggests the architecture is platform-independent and adaptable. However, as a Research and Innovation Action (RIA), the outputs are validated prototypes rather than production-ready products. Scaling to commercial volumes would require additional engineering and certification work.
What is the IP situation — can we license this technology?
The consortium of 8 partners across 6 countries includes 3 industry partners who likely hold commercial exploitation rights. IP ownership and licensing terms would need to be negotiated with the coordinating institution (IDRYMA TECHNOLOGIAS KAI EREVNAS in Greece) or the specific partner that developed the component you need. Based on available project data, no open-source licensing model is explicitly mentioned.
Does this work with our existing systems or require a full redesign?
SHARCS specifically addressed the challenge of securing legacy applications alongside new builds. The project's objective included systematically analyzing and extending existing hardware and software layers, which suggests backward-compatible integration paths were explored. However, full end-to-end security may require hardware upgrades depending on your current infrastructure.
How does this compare to just adding software security?
The core premise of SHARCS is that software-only security leaves fundamental gaps — if the hardware layer is compromised, no amount of software patching helps. The project demonstrated that securing every layer starting from the processor gives substantially stronger protection. This is particularly relevant for industries like automotive and medical where physical access to devices makes software-only defenses insufficient.
What regulatory standards does this address?
Based on available project data, SHARCS targeted security-critical applications in medical, cloud, and automotive domains, all of which face increasing cybersecurity regulation. While the project predates some current regulations (it ran 2015-2017), the secure-by-design approach aligns with principles now required by the EU Cyber Resilience Act, medical device MDR cybersecurity requirements, and automotive UN R155.
Is the project team still active and available for collaboration?
SHARCS officially closed in December 2017. The coordinating institution (IDRYMA TECHNOLOGIAS KAI EREVNAS, also known as FORTH in Greece) is a major research foundation that remains active. Several consortium partners are industry players who may have continued developing the technology commercially. The project website at sharcs-project.eu may have updated contact information.
Who built it
The SHARCS consortium brings together 8 partners from 6 countries (Germany, Greece, Gibraltar, Israel, Netherlands, Sweden), with a healthy 38% industry participation ratio — 3 industry players alongside 3 universities and 2 research organizations. The mix signals that academic research was tested against real industry requirements, though only 1 partner is an SME. The coordination by FORTH (Greece), one of Europe's largest research foundations, adds institutional weight but also means commercialization likely depends on the industry partners taking results to market. For a business buyer, the multi-country, multi-sector validation (medical, cloud, automotive) is a strength — it suggests the technology is genuinely platform-independent rather than tied to one vendor's ecosystem.
- IDRYMA TECHNOLOGIAS KAI EREVNASCoordinator · EL
- STICHTING VUparticipant · NL
- ELEKTROBIT AUTOMOTIVE GMBHparticipant · DE
- TECHNISCHE UNIVERSITAET BRAUNSCHWEIGparticipant · DE
- ONAPP LIMITEDparticipant · GI
- NEURASMUS BVparticipant · NL
- IBM ISRAEL - SCIENCE AND TECHNOLOGY LTDparticipant · IL
- CHALMERS TEKNISKA HOGSKOLA ABparticipant · SE
IDRYMA TECHNOLOGIAS KAI EREVNAS (FORTH) in Greece coordinated the project. Use Google to find the principal investigator's contact via the project acronym and institution name.
Talk to the team behind this work.
Want to know if SHARCS technology fits your security challenge? SciTransfer can connect you with the right consortium partner and prepare a tailored briefing on licensing options.