MetaNoria

MetaNoria is an engine designed to manage metadata throughout the metadata lifecycle and the controlled distribution of metadata, based on embedded security models and data ownership enforcement. The security models are configured by system governance policy in addition to user driven security interests.

MetaNoria is built for change because it captures, distributes and consumes metadata. So as new or modified metadata is processed new capability is enabled. For example, if a change is desired to an Enterprise Resource Planning (ERP) system, metadata instructing the change, is sent from institutional metadata site and executed bt an API designed to effect the change to the ERP.

The metadata contains ownership information that is enforced at the consuming site (user of data) consequently, at the request of the data owner, data can be recalled or set to expire. MetaNoria generates metadata based on user selection of “canned” artifacts. It also supports the definition of artifacts that are unique to the user; provided the user follows a metadata definition language provided and supported by MetaNoria.

Distribution of metadata is managed and governed by the interface to MetaNoria such that metadata is controlled at the distribution site and consuming site based on security models. Note: Without metadata access and retention, associated data cannot be stored or defined. Therefore MetaNoria controls the flow of data securely at the source of data generation, distribution of data, and storage of data throughout the lifecycle of the metadata.

MetaNoria Metadata Engine Product Features built for change

  • The MetaNoria integration methodology embraces organizational structure with respect to enterprise security policy and as it relates to data and process ownership, access authorization, and governance.
  • It provides an organizational architecture definition and integration capability that an information architect can use to define information and integrate it with other information sets and architectures.
  • The security profile concept, articulated within MetaNoria and implemented via distributed MetaNoria instances, allows a security architect to emplace process level security by flowing enterprise security architecture down to the lowest application components.
  • Using MetaNoria to enforce security policy ontomessaging traffic, user access, and service invocations enables a web services, SOA, or cloud computing infrastructure as "trusted", to protect and secure data.
  • MetaNoria brings security life cycle management to the business and application life cycle management processes, at the system-of-systems (SoS) level.
  • SoS level security life cycle management is required to address the challenges of information accuracy, traceability, context sensitivity, and obsolescence as in distributed and loosely coupled systems, for the data to be secured, it first has to be understood.
  • It enables the management of system dynamics, integrating controls with security profile concepts, and enabling process level governance reporting and response.
  • Web service security products interoperability using a single authoritative set of configuration input data to prevent gaps in security coverage.
  • Model driven security control and audit for SOA-enabled loosely coupled environments.
  • Web service invocation audit, reporting, and control based on the user, data, and service rights.
  • Model driven policy to inject policy into the cloud, per application and business needs, independent of cloud provider.
  • Provide persistent and consistent integration that readily accommodates changes to data, processing environments, and repository locations.