AllegroGraph Enterprise Security and Management

Franz AllegroGraph v4 represents the first Semantic Technology Database with OLTP, ACID compliance and Enterprise Management functionality. AllegroGraph Enterprise Security and Management (ESM) provides the mission critical functionality that organizations need to support 24/7/365 operations. AllegroGraph has received a Certificate of Networthiness for the product to run on the Department of Defense .mil network.

This document gives and overview of security in AllegroGraph. See Security Implementation for implementation details.

AllegroGraph ESM includes the following:

Transport Layer Security

Access to an AllegroGraph database server can be obtained via AllegroGraph’s RESTful interface (for HTTP and HTTPS clients), through AllegroGraph’s built-in web interface – AGWebView, and through a local Lisp client application

All client network access to AllegroGraph occurs though the product’s HTTP and HTTPS RESTful interfaces. The AllegroGraph interface, and RESTful interfaces in general, are remarkable in that they are by definition client-server, stateless, cacheable and provide a uniform interface identifying system resources in the client request.

AllegroGraph clients can connect directly to the server via HTTP, sending and receiving clear text. AllegroGraph clients also have the ability to send and receive encrypted requests.

SSL and TLS

When an AllegroGraph session is established over Secure Sockets Layer (SSL), the server shares a public key with the client which is used to encrypt subsequent requests. AllegroGraph supports TLS versions 1.0, 1.1, and 1.2.

AllegroGraph utilizes FIPS 140-2 compliant encryption for data in transit. Reference http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf.

X.509 Certificates

The server provides an X.509 certificate to the client during the SSL/TLS handshake when the connection is established. Therefore the client can check the contents of the certificate if desired.

Management Access Control

AGWebView provides a GUI management and data access interface to AllegroGraph v4, as we describe in Security Implementation. The web-browser based interface allows the system administrator to manage access control to individual databases, maintain users and roles, and control the Warm Standby and Replication interfaces.

Configuration of Databases and Catalogs

Database and collections of databases are effectively managed through AGWebView. Control over placement of the catalogs, individual databases, and server settings is managed during initial server configuration.

Management of JavaScript and Lisp Stored Procedures

Both JavaScript and Lisp stored procedures are supported. The user manages stored procedures through AGWebView.

User Management

The system administrator is given fine-grain control over creation and management of users, passwords and roles through the AGWebView interface.

There are several predefined user attributes, including Superuser, Start Sessions, Eval (stored procedures) and (control) Replication.

For each user and role, the administrator can manage these attributes and access to individual databases. Access to databases can be granted per database, a portion of a catalog or for the entire database server.

Programmatic System Management

Through the RESTful interface to AllegroGraph, all the management functions of the product are exposed via HTTP(S), Java, Python, Lisp and others. Customer organizations can take advantage of AGWebView, or for embedded solutions provide their own custom interface to AllegoGraph security and management.

Summary:

Manage User Attributes

Administrative Functionality

Data Access - Allegro Graph v4.3 (Triple Level Security)

As RDF stores become more entrenched in enterprise applications, increased security and improved fine-grained control of access to data is required. To support this, AllegroGraph v4.3 introduces Triple/Quad Level Security Filters, which are described in this section of Security Implementation.

With Security Filters the system administrator is able to grant user access to the entire store, or restrict access to a limited and filtered view of the database.

Security Filters can be applied to individual databases for all add/delete/query operations, per user and per role. You specify which values of the subject, predicate, object, or graph should be allowed or disallowed and then query responses are filtered appropriately, and attempts to add or delete filtered triples fail.

Key Security Filter Features: