Digital Play 11 - Manage security and privacy through reusable processes

[ClaireReinken]

• Contact the appropriate privacy or legal officer of the department or agency to determine whether a System of Records Notice (SORN), Privacy Impact Assessment, or other review should be conducted
• Determine, in consultation with a records officer, what data is collected and why, how it is used or shared, how it is stored and secured, and how long it is kept
• Determine, in consultation with a privacy specialist, whether and how users are notified about how personal information is collected and used, including whether a privacy policy is needed and where it should appear, and how users will be notified in the event of a security breach
• Consider whether the user should be able to access, delete, or remove their information from the service
• “Pre-certify” the hosting infrastructure used for the project using FedRAMP
• Use deployment scripts to ensure configuration of production environment remains consistent and controllable

[ClaireReinken]

•Contact the appropriate privacy or legal officer of the department or agency to determine whether a System of Records Notice (SORN), Privacy Impact Assessment, or other review should be conducted We deemed this requirement not relevant to this prototype. •Determine, in consultation with a records officer, what data is collected and why, how it is used or shared, how it is stored and secured, and how long it is kept Test data does not have any information that is sensitive user data. The sample user accounts created to associate shopping carts and orders, were pre-loaded. There is no privacy issues. Our team augmented the sample data provided with dummy data in order to demonstrate additional functionality. •Determine, in consultation with a privacy specialist, whether and how users are notified about how personal information is collected and used, including whether a privacy policy is needed and where it should appear, and how users will be notified in the event of a security breach Based on our legal and privacy review, we have not identified any privacy issues. •Consider whether the user should be able to access, delete, or remove their information from the service The data from this prototype was not sensitive to any real user account information (across HTTP session) therefore was not in-scope to be removed. •“Pre-certify” the hosting infrastructure used for the project using FedRAMP We are using the widely used Microsoft Azure cloud environment, which earned a P-ATO at the High Impact Level, the highest bar for FedRAMP accreditation. •Use deployment scripts to ensure configuration of production environment remains consistent and controllable Container and virtual machine based deployment controlled by CI platform with customized script to ensure the configuration and resource are consistent and controllable for production. In a larger project, other configuration tools (e.g., Chef, Puppet, or Ansible) would also be used. Resource creation was scripted for internal servers. Azure templates generated can be modified and reused to this end. Containers ensure configuration, but we did not implement any form of desired state configuration for the prototype. VM and hosting are not traditionally part of Continuous Integration. CI and CD are generally only applied to software.