... | @@ -63,11 +63,30 @@ These include: |
... | @@ -63,11 +63,30 @@ These include: |
|
- Common facades for OSDU services and their utilities, including Search, Legal, notification, partitioning etc..
|
|
- Common facades for OSDU services and their utilities, including Search, Legal, notification, partitioning etc..
|
|
- Common logging clients
|
|
- Common logging clients
|
|
- Common exception handling
|
|
- Common exception handling
|
|
- Common HTTP/HTTPS and REST client utilities,
|
|
- Common HTTP/HTTPS and REST client utilities
|
|
|
|
- Provider specific core dependencies, for AWS, Azure, Google and IBM
|
|
- etc..
|
|
- etc..
|
|
|
|
|
|
|
|
A couple of high level assertions about the core code:
|
|
|
|
- The code is mainly written in Java ((1.8 for now)
|
|
|
|
- Requires Maven to build
|
|
|
|
- Uses springboot as the universal hosting environment across all CSPs
|
|
|
|
- Each service has a complete list of dependencies in the provider implementation's POM.XML, including CSP specific and other service dependencies.
|
|
|
|
- All code has tests. Unit and integration tests use Junit (and sometimes cucumber)
|
|
|
|
|
|
### Security, Entitlement and Compliance
|
|
### Security, Entitlement and Compliance
|
|
|
|
|
|
|
|
Security of the system is a shared responsibility. The cloud platform, the provider, the platform operator, and the platform itself have their own responsibility to ensure end-to-end security of the OSDU.
|
|
|
|
|
|
|
|
The OSDU R3 has a provider specific entitlement service that manages user access to the data and services. The entitlement service per provider is developed as part of the code base and available as part of the core services. This services is an RBAC service and depends on user specific ACLs created and managed by the platform admin.
|
|
|
|
|
|
|
|
The legal services provides a simple rule engine to manage data governance and other data compliance rules.
|
|
|
|
|
|
|
|
There is currently an incubating service that aims to use policies to manage both user entitlements and compliance rules. This is in development but is not expected in the scope for OSDU R3.
|
|
|
|
|
|
|
|
Other aspect of security involve security standards of the platform itself. These are captured as security requirements and documented and certified ahead of the release. For more information on the security parameters and the adherence, consult this [document](http://osdu.projects.opengroup.org/subcommittees/info-sec/work-products/public-security-documentation/html/OSDU-InfoSec.html)
|
|
|
|
|
|
|
|
|
|
### Test Data
|
|
### Test Data
|
|
|
|
|
|
### Platform Validation
|
|
### Platform Validation
|
... | | ... | |