Develop and operate the Sepior Key Management infrastructure, which is comprised of the MgmtServer(s), AuthServer(s), plus some monitoring of deployed KeyServer(s). On top of this a traditional infrastructure for support (FAQ, ticketing, forums for users etc.) must be set up. This is based on D1+D2.
Integration and test of the Sepior Key Management service with integration partners and end customers. More frequent integration and testing will be conducted against Partisia’s solutions (as explained in Section 2.8, the relationship between Sepior and Partisia allows for this). For the beta version released in year 1, the aim is do this with a high degree of manual labour (i.e. consultants), but for v1 (year2) the aim is to automate as much of the process as possible to reduce the burden of enrolling new customers.
Plugin(s) for third party services (D1.6) available for use with version 1 of Sepior Key Management.
Improving the existing Sepior Storage system while also using it as the first system for testing new versions of the software described in deliverable D1+D2 (allowing us to provide live test in a system completely under our own control).
Original text: Improving the existing Sepior Storage system while also using it as the first system for testing new versions of the software developed (allowing us to provide live test in a system completely under our own control). New text: As commercial efforts related to the Sepior Storage solution have been stopped (see motivation in previous semiannual report plus support documents for amendment request), we’re requesting that we spend the associated effort on implementing plugins for other third party cloud services based on customer demand. As earlier reported, we have already implemented a simple plugin for Amazon S3, and are looking towards similar plugins for (e.g.) services such as Microsoft Azure and Google Compute Engine, and possibly other AWS services.
Version of the solution deployed.
Integration and Test of Sepior Storage against beta from deliverable D7.