Data at Rest. Vendor agrees that any and all OSUWMC data will be stored, processed, and maintained solely on designated servers and that no OSUWMC data at any time will be processed on or transferred to any portable or laptop computing device or any portable storage medium, unless that storage medium is encrypted using no less than 128 bit encryption key.
Data at Rest. Druva agrees to encrypt customer data at rest in the Druva cloud service using industry best practices of a unique Advanced Encryption Standard (AES) encryption key or equivalent per customer. This unique encryption key per customer will provide logical and cryptographic segmentation of Customer Data.
Data at Rest. Bynder shall ensure the appropriate encryption of data at rest.
Data at Rest processing This layer provides different execution engines for scalable, distributed and parallel algorithm execution. It implements different machine learning and pattern recognition algorithms on top of processing layer and technologies such as Hadoop, Spark and CEP; Hadoop is the pivot point of the system which runs parallel, distributed batch training jobs using map-reduce algorithms. It is directly controlled through Oozie and data used as input for the jobs is stored in HBASE.
Data at Rest processing The way of configuring STH through docker needs to set the following environmental variables: • STH_HOST, the STH host will be the IP where start the service, • DB_URI, DB_USERNAME, DB_PASSWORD, those parameters are in charge of connect STH with the database. Other useful variables like SHOULD_STORE or TRUNCATION_EXPIRE_AFTER, can help to store only the information necessary. More information about STH configuration here in the following link (xxxx://xxxxxx-xxx-xxxxx.xxxxxxxxxxx.xx/en/r5_fiware/running/). Knowage must be executed with MySQL, the simplest way is with docker. Docker permits connect Knowage to MySQL using containerized versions of both services. The values that must contain in the configuration file are: MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE, MYSQL_ROOT_PASSWORD. The environment variable to keep in mind is PUBLIC_ADDRESS, without it settled up, Knowage will show error messages. All remaining settings are established in the graphical interface (users, roles, menus).
Data at Rest processing STH must be launched with other components like Cygnus and MongoDB in order to work properly. Using this configuration STH values generated can be retrieved directly from the MongoDB instance. In order to better understand the scenario, a flow example is depicted in the figure below. Cygnus must be linked with STH and MongoDB generating raw and aggregated data that will be stored in the database. This generated data has a prefix that STH should be expecting in the database, in this way STH through it REST API using the values stored in the MongoDB instance. The REST API makes possible to get raw data between two dates, before a date or after a date and the same with aggregated data. The API response with a JSON (NGSI). STH is compatible with both NGSI9 and NGSI10, the standard to RESTful API by FIWARE. As can be seen in the next diagram, a client asks to Xxxxx to establish a subscription, REST API of Orion, responds OK; every time that an entity of Orion changes, Xxxxx will notify Cygnus and this will be added data to the MongoDB instance, then STH can access to information with a database query. Just like as STH, Knowage have functions to show data stored on database, as can see on the diagram below. To launch knowage, it is necessary to run MySQL, so that all menus, users, documents or any changes made through the graphical interface will be stored in this database. Regardless of which database is used for data collection for subsequent sampling. Once this is done it is possible to launch the containers. More information about launching the container can be found here: (xxxxx://xxx.xxxxxx.xxx/r/knowagelabs/knowage-server- docker/)Futhermore, the data received as an Orion’s entity, is detected like NGSIv2 provided of course is activated the option from interface. All functions are performed through the graphical interface, once the services have started, Knowage is accessible with the next URL “<HOST- IP>:<PORT-INDICATED>/knowage”. Users can view documents or dashboards generated by administrators. There are different roles that allow restricting or allowing access to the different parts of the interface; this interface is very powerful and complete. Knowage do not possess REST API. More information about how to use this tool can be found in the following community manual of use about graphical interface of Knowage: (xxxxx://xxxxxxxx.xxxxx.xx0.xxx/knowage/Knowage_6.x_CE_Manual.pdf)
Data at Rest. If sensitive data (e.g credentials, personally identifiable information of Amazon employees or Amazon customers, etc.), resides on the devices and systems it must be encrypted at rest.
Data at Rest. 6.1 The use of the Advanced Encryption Standard (AES) or stronger is used for symmetric encryption.
Data at Rest. The Contractor shall ensure encryption of Personal Data and Non-Public Data within the Contractor’s possession or control is consistent with validated cryptography standards as referenced in Federal Information Processing Standard (FIPS) 140 Publication Series.
Data at Rest. The contractor shall ensure that an approved DOD product is utilized for Data at Rest (DAR) that is stored on mobile computing devices such as laptops and personal digital assistants (PDAs), or removable storage media. The cryptography shall be National Institute of Standards and Technology (NIST) Federal Information Processing Standard 140-2 (FIPS 140-2) compliant and a mechanism shall be established to ensure encrypted data can be recovered in the event the primary encryption system fails. CONTRACT NO. N00178-14-D-7931 DELIVERY ORDER NO. N6833519F3000 PAGE 23 of 112 FINAL
