Secure publication to the DDS - Revision history

JoshuA at 08:41, 9 April 2021

2021-04-09T08:41:39Z

← Older revision		Revision as of 08:41, 9 April 2021
Line 8:		Line 8:
	=== SFTP Pull ===		=== SFTP Pull ===

	~~GPIT~~ Futures IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.		GP IT Futures IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.

	=== SFTP Push ===		=== SFTP Push ===

JoshuA at 08:41, 9 April 2021

2021-04-09T08:41:23Z

← Older revision		Revision as of 08:41, 9 April 2021
Line 8:		Line 8:
	=== SFTP Pull ===		=== SFTP Pull ===

	~~GPSoC~~ IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.		GPIT Futures IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.

	=== SFTP Push ===		=== SFTP Push ===

DarrenS at 09:39, 22 June 2020

2020-06-22T09:39:31Z

← Older revision		Revision as of 09:39, 22 June 2020
Line 14:		Line 14:
	The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

	=== HTTPS Post ===		=== HTTPS REST Post ===

	The data is posted to the DDS and ~~the~~ onto a publisher specific ~~SFTP folder~~ structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is posted to the DDS and then onto a publisher specific data structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

	=== MLLP Send ===		=== MLLP Send ===

JoC at 12:04, 15 May 2020

2020-05-15T12:04:07Z

← Older revision		Revision as of 12:04, 15 May 2020
Line 24:		Line 24:
	===AWS Security===		===AWS Security===

	As a hosting organisation, AWS has in place over 50 security and compliance certifications including ISO 27001, 27017, 27018; PCI DSS; SOC 1/2/3; and Cyber Essentials Plus.The DDS is built on this platform and makes use of multiple enhanced features to secure the data; these include encrypting all networks to at least TLS 1.2 with high strength ciphers, ensuring all data at rest (such as in databases) or data in transit (such processing queues) is encrypted, administrative access is controlled using VPN with 2FA, access controls, and all access to the systems is logged & audited.The system has been designed to exceed the requirements set out in the NHS Data Security Protection Toolkit.		As a hosting organisation, AWS has in place over 50 security and compliance certifications including ISO 27001, 27017, 27018; PCI DSS; SOC 1/2/3; and Cyber Essentials Plus.

			The DDS is built on this platform and makes use of multiple enhanced features to secure the data; these include encrypting all networks to at least TLS 1.2 with high strength ciphers, ensuring all data at rest (such as in databases) or data in transit (such processing queues) is encrypted, administrative access is controlled using VPN with 2FA, access controls, and all access to the systems is logged & audited.

			The system has been designed to exceed the requirements set out in the NHS Data Security Protection Toolkit.

	===HSCN Certification===		===HSCN Certification===

	The Discovery platform has an HSCN to AWS connection that has been certified. The connection is provided through our IG agreement with Tower Hamlets CCG ODS code 08V.		The Discovery platform has an HSCN to AWS connection that has been certified.

			The connection is provided through our IG agreement with Tower Hamlets CCG ODS code 08V.

JoC at 12:03, 15 May 2020

2020-05-15T12:03:11Z

← Older revision		Revision as of 12:03, 15 May 2020
Line 6:		Line 6:
	* MLLP Send		* MLLP Send

	== SFTP Pull ==		=== SFTP Pull ===

	GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.		GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.

	== SFTP Push ==		=== SFTP Push ===

	The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

	== HTTPS Post ==		=== HTTPS Post ===

	The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

	== MLLP Send ==		=== MLLP Send ===

	Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.		Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.

	==AWS Security==		===AWS Security===

	As a hosting organisation, AWS has in place over 50 security and compliance certifications including ISO 27001, 27017, 27018; PCI DSS; SOC 1/2/3; and Cyber Essentials Plus.The DDS is built on this platform and makes use of multiple enhanced features to secure the data; these include encrypting all networks to at least TLS 1.2 with high strength ciphers, ensuring all data at rest (such as in databases) or data in transit (such processing queues) is encrypted, administrative access is controlled using VPN with 2FA, access controls, and all access to the systems is logged & audited.The system has been designed to exceed the requirements set out in the NHS Data Security Protection Toolkit.		As a hosting organisation, AWS has in place over 50 security and compliance certifications including ISO 27001, 27017, 27018; PCI DSS; SOC 1/2/3; and Cyber Essentials Plus.The DDS is built on this platform and makes use of multiple enhanced features to secure the data; these include encrypting all networks to at least TLS 1.2 with high strength ciphers, ensuring all data at rest (such as in databases) or data in transit (such processing queues) is encrypted, administrative access is controlled using VPN with 2FA, access controls, and all access to the systems is logged & audited.The system has been designed to exceed the requirements set out in the NHS Data Security Protection Toolkit.

	==HSCN Certification==		===HSCN Certification===

	The Discovery platform has an HSCN to AWS connection that has been certified. The connection is provided through our IG agreement with Tower Hamlets CCG ODS code 08V.		The Discovery platform has an HSCN to AWS connection that has been certified. The connection is provided through our IG agreement with Tower Hamlets CCG ODS code 08V.

JoC at 12:02, 15 May 2020

2020-05-15T12:02:32Z

← Older revision		Revision as of 12:02, 15 May 2020
Line 1:		Line 1:
	Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:		Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:

			* SFTP Pull
			* SFTP Push
			* HTTPS Post
			* MLLP Send

	== SFTP Pull ==		== SFTP Pull ==

JoC at 12:01, 15 May 2020

2020-05-15T12:01:25Z

← Older revision		Revision as of 12:01, 15 May 2020
Line 16:		Line 16:

	Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.		Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.

			==AWS Security==

			As a hosting organisation, AWS has in place over 50 security and compliance certifications including ISO 27001, 27017, 27018; PCI DSS; SOC 1/2/3; and Cyber Essentials Plus.The DDS is built on this platform and makes use of multiple enhanced features to secure the data; these include encrypting all networks to at least TLS 1.2 with high strength ciphers, ensuring all data at rest (such as in databases) or data in transit (such processing queues) is encrypted, administrative access is controlled using VPN with 2FA, access controls, and all access to the systems is logged & audited.The system has been designed to exceed the requirements set out in the NHS Data Security Protection Toolkit.

			==HSCN Certification==

			The Discovery platform has an HSCN to AWS connection that has been certified. The connection is provided through our IG agreement with Tower Hamlets CCG ODS code 08V.

Admin at 16:47, 8 April 2020

2020-04-08T16:47:02Z

← Older revision		Revision as of 16:47, 8 April 2020
Line 4:		Line 4:

	GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.		GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.


	== SFTP Push ==		== SFTP Push ==

	The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.


	== HTTPS Post ==		== HTTPS Post ==

	The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.		The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.


	== MLLP Send ==		== MLLP Send ==

	Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.		Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.

JoC at 17:16, 25 March 2020

2020-03-25T17:16:41Z

← Older revision		Revision as of 17:16, 25 March 2020
Line 1:		Line 1:
	Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:		Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:

	~~[[SFTP Pull]]~~
	~~[[SFTP Push]]~~
	~~[[HTTPS Post]]~~
	~~[[MLLP Send]]~~


	== SFTP Pull ==		== SFTP Pull ==

JoC: Created page with "Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways: SFTP Pull SFTP Push HTTPS Post MLLP Send == SFTP..."

2020-03-25T17:16:19Z

Created page with "Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways: SFTP Pull SFTP Push HTTPS Post MLLP Send == SFTP..."

New page

Data is transferred, via HSCN, into the DDS HSCN connected AWS instance in one of the four following ways:

[[SFTP Pull]]
[[SFTP Push]]
[[HTTPS Post]]
[[MLLP Send]]

== SFTP Pull ==

GPSoC IM1 pairing directly with the publisher’s system supplier. The data is pulled by the DDS from the suppliers SFTP and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link. Data from EMIS is pgp encrypted at source.

== SFTP Push ==

The data is pushed from the publisher's SFTP into the DDS and then onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

== HTTPS Post ==

The data is posted to the DDS and the onto a publisher specific SFTP folder structure in Discovery’s AWS instance over a TLS 1.2 encrypted link.

== MLLP Send ==

Messages are posted over VPN TLS 1.2 encrypted links into the DDS HL7 receiver and then onto Discovery’s AWS instance.