Gemom
From Wikipedia, the free encyclopedia
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to its deletion for any reason. To avoid confusion, it helps to explain why you object to the deletion, either in the edit summary or on the talk page. If this template is removed, it should not be replaced. The article may be deleted if this message remains in place for five days. This template was added 2008-06-12 08:53; five days from then is 2008-06-17 08:53. If you created the article, please don't take offense. Instead, consider improving the article so that it is acceptable according to the deletion policy. Author(s) notification template: {{subst:prodwarning|Gemom}} ~~~~ |
A FP7 European Project - January 2008 – June 2010
As messaging connects various system actors together and often spans various localised or distributed domains it is at the heart of security related issues.
From the R&D perspective the mission for GEMOM is to research, develop and deploy a prototype of a messaging platform that is selforganising and self healing and provides secure end to end transactions. GEMOM is resilient and could utilise redundant modules (hot-swap or switchover) instantaneously without information loss. All these features allow specialist, independent system actors such as watch-dogs, security/situation monitors, routers, and optimisers to remove or replace compromised nodes from the broader network instantly without compromising higher level functionality.
GEMOM offers a messaging infrastructure which will enable far cheaper solutions as there is no need for heavy investment into infrastructure and assurance against security vulnerabilities and erroneous input vulnerabilities.
[edit] Objectives
The core scientific focus of GEMOM is the significant and measurable increase in end-to-end intelligence, security and resilience of complex, distributed information systems.
The primary objective of GEMOM is to research, develop and deploy a prototype of a messaging platform that is evolutionary, self-organising, self healing, scalable and secure.
GEMOM will be resilient and able to utilise redundant modules (hot-swap or switchover) instantly without information loss. These resilience features will allow specialist, independent system actors, viz. watch-dogs, security and situation monitors, routers, and other optimisers, to remove or replace compromised nodes from the broader network instantly without compromising higher level functionality.
GEMOM considers the Publish-Subscribe variant of Message Oriented Middleware to be the predominant one and will focus on issues surrounding that kind of messaging. For completeness GEMOM will provide a synchronous Request and Reply overlay as well.
The advances that GEMOM proposes to make to the area of messaging revolve around the notion of a “fault”. GEMOM extends the notion of fault to include compromised security or inadequate bandwidth availability in the first iteration and compromised abstract notion of “resource” in its final iteration.
Core research focus of GEMOM is ultra-resilience of messaging. GEMOM analyses the following core issues that underpin ultra resilience and so could compromise it as well:
Reliability of message sourcing and delivery. To accommodate this GEMOM offers to handle redundant message feeds, where needed, and redundant delivery paths. In the event of failure switch over to redundant resource would be effectively instantaneous and with no information loss. In addition to entire message broker redundancy GEMOM offers redundancy of certain subsets or messaging segments. As part of its self-healing when redundant components are switched to and used, GEMOM finds and primes other nodes, feeds or paths as new redundant components. In short, GEMOM ensures that there are no single points of failure even as new nodes become compromised and so rendered alien and isolated.
Scalability with respect to message volumes. GEMOM will ensure that scalability is not compromised as redundancy is utilised. Switchover to redundant components will preserve scalability.
Replicating structural and dynamic properties of security metrics. One particular GEMOM setup might be configured with a certain security layout in place. GEMOM will research issues and deploy innovative solutions to ensure that the security profiles of overall system and individual message paths and dynamics are not compromised as a result of failovers. Namely, GEMOM will be capable of fully replicating structural and dynamic properties of security policies.
Process zoning and overall encapsulation to an arbitrary level. Where the economy of the implemented solution carries higher weighting GEMOM allows for separation of cheaper messaging (still scaleable, resilient and self-healing) on one side but fully fledged monitoring, management and maintenance on another side. Namely, GEMOM allows for process zoning and overall encapsulation to an arbitrary level.
Pre-emptive vulnerability testing and vulnerability updating. Whether by accident or as the result of deliberate cyber attack, components executing on different computers across different trust boundaries may interact in an unforeseen way or expose a vulnerability that an attacker could exploit. Pre-emptive detection of known and unknown vulnerabilities needs tools that can analyse the deployed middleware, client server applications and web service based applications both statically and dynamically, and this will be provided by GEMOM. This will also allow checking for new vulnerabilities when they are reported.
Message oriented middleware acts at a trust boundary and is often not just a passive entity. It combines and transforms data and sends it to other components. Message oriented middleware is therefore an important location to be guarded and for guarding the components with which it interacts. GEMOM will investigate and develop novel techniques that can automate the intelligent checking of the deployed GEMOM system for robustness to misconfiguration, erroneous data and vulnerabilities to cyber attacks in the context of the deployed environment.
Here is the link to the project: The Gemom Project Website
