Thirteen things that need to be good to make a secure Cross Domain Solution (CDS).
Pages
Page 5 of 15
Protect against the unauthorised export of information
A well-engineered CDS, with export functionality, should protect against the unauthorised export of information.
Defensive techniques
When exporting data, the amount of data exported should be kept to the minimum necessary. In practice, this will depend on the types of data being exported and the purposes of the exports.
Data exports should not contain any superfluous user data or machine generated information, other than that specifically required for the intelligibility of the exported data.
Export of data should be limited to those authorised for business needs, and the CDS should authenticate these exports.
Where user-generated data is to be exported, the CDS should ensure that release of the data is appropriately authorised, either by the originating user or other authorising users. Authentication by the CDS, described later in this document, should be used to support this authorisation.
Authorisation to release information (or 'release authorisation') should take into account business processes required to sanction information release.
There should be a strong binding between data authorisation and data release, such that only approved data is released outside of the system.
Systems that need to enforce synchronous bi-directional communication (transactional query-response traffic such as HTTP requests or SQL queries) should correlate requests and responses, so that a response cannot pass without a corresponding request of the correct type.
