(DTERP-1908) Security

Outboard integration - Security concept for decentralized deployment

Outboard integration - Security concept for centralized deployment

Outboard’s security concept distinguishes two borders of data flow:

1. Archiving client to Outboard,
2. Outboard to External Storage

Security concept of communication – Archiving client to Outboard

To prevent unauthorized access Datavard Outboard DataTiering is built to comply with the SAP authorization concepts, where each connection carries out an authorization check.

Authorization object being validated when operating with the Outboard is:

• /DVD/CRP – permitted activities:
  • 03 – Display
  • 16 – Execute
  • 23 – Maintain

However, access is gained via the open HTTP or HTTPS interface. URLs are secured with signature, so they allow only authorized access to stored content and, correspondingly, so that forged requests are rejected.

Datavard Outboard DataTiering decodes the signature and compares it with the URL it received. The service only executes the request if the URL and the signature were matching.

Level of security at this border is generally lower than at the outbound border towards external storage because its typically within internal corporate network.

Security concept of communication – Outboard to External Storage

Outbound communication with an external storage, MUST be secured. This is achieved using secured protocol that is storage platform-specific and therefore depends on API utilized by corresponding Storage Management connector implementation (e.g. HTTPS, Secured NFS, etc.). Additionally, authorized access is controlled using platform-specific authentication / authorization concept, e.g. using Kerberos, Active Directory and others together with user permission management.

Authorizations & Segregation of duties

The Outboard Service requires 2 users

• Maintenance: Administrator dialog user
• Operation on data: Service user – used in Outboard HTTP Service definition