System Security Functions: Recommendations

• Policy: Develop an information security policy that delineates the roles and responsibilities of the Program staff and participants with respect to the Registry and its data. Include appropriate procedures to ensure local site data and software is properly managed.
• Security Levels for Applications: General Reader, General User, Site Manager (Sample screens: Child Lookup, General User screen, "Critical Fields" modification screen)
• Harden Server Against Network Attack: Several steps can be taken to harden the server against attack from the Internet.
• Train Staff Appropriately: Appropriate systems and operations training needs to be provided for staff, including backup personnel. Consulting assistance needs to be provided when necessary.
• Physically Secure the Server: The database server should be kept in a locked facility, alarmed whenever left unattended. Uninterrupted power should be provided. Data backups (including off-site storage of backup media) should be in place and functioning. Restoration from backups should be periodically tested.
• Prevent Promiscuous Access to Data: Via Oracle's Secure Network Services, the full client/server data stream can be encrypted to prevent even accidental disclosure of data by promiscuous capture on the network. In addition, the IP subnet upon which the server is attached should be a "trusted" subnet: all computers on the subnet should be used and administered by "trusted" personnel. In addition, the network topology for the pilot should have Project participants attached to this same subnet rather than come into the server over the public Internet.