Changes for page SFTP Known Hosts

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,6 +1,6 @@
1	1	{{container}}{{container layoutStyle="columns"}}(((
2	2
3		-In the last microlearning, we discussed how to connect to an SFTP from eMagiz. In this microlearning, we want to expand our knowledge and look at a more complex security configuration when connecting to SFTP instances. The configuration we are talking about is the private key configuration.
	3	+In an earlier [[microlearning>>Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.intermediate-file-based-connectivity-sftp-connectivity||target="blank"]], we discussed how to connect to an SFTP from eMagiz. Later on we zoomed in on an alternative security method to authenticate yourself at the SFTP. More on this can be found in this [[microlearning>>Main.eMagiz Academy.Microlearnings.Intermediate Level.File based connectivity.intermediate-file-based-connectivity-sftp-security||target="blank"]]. In this microlearning, we want to expand our knowledge and look at a way to store the unique fingerprint of the SFTP to avoid that someone else can pretend to be the SFTP when you want to send data (i.e. a "man in the middle attack").
4	4
5	5	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6	6
...	...	@@ -11,49 +11,57 @@
11	11
12	12	== 2. Key concepts ==
13	13
14		-This microlearning is about SFTP security.
	14	+This microlearning is about SFTP known host files.
15	15
16		-By SFTP security, we mean: Making sure that the SFTP we connect to knows that we are indeed eMagiz
	16	+By SFTP known hosts, we mean: Making sure that we are certain that we connect to the correct SFTP to prevent data theft as a result of a "man in the middle" attack.
17	17
18		-* Private key is unique per client
19		-* Private key should only be known to the client
20		-* Public key should be known to the SFTP (server), so they trust us when we set up the communication
21		-* A private key comes with a passphrase
	18	+* Each SFTP has a unique fingerprint that identifies the SFTP.
	19	+* To prevent a "man in the middle" attack, this fingerprint needs to be stored client side.
	20	+* There are two distinct methods to generate the known hosts file.
22	22
23		-== 3. SFTP Security ==
	22	+== 3. SFTP Known Hosts ==
24	24
25		-In the last microlearning, we discussed how to connect to an SFTP from eMagiz. In this microlearning, we want to expand our knowledge and look at a more complex security configuration when connecting to SFTP instances. The configuration we are talking about is the private key configuration.
	24	+In this microlearning, we want to expand our knowledge and look at a way to store the unique fingerprint of the SFTP to avoid that someone else can pretend to be the SFTP when you want to send data (i.e. a "man in the middle attack"). To retrieve the unique fingerprint of an SFTP you first need to connect to the SFTP in question. This way you can retrieve the unique fingerprint and secure it in a file for future use to prevent the "man in the middle attack".
26	26
27		-* Private key is unique per client
28		-* Private key should only be known to the client
29		-* Public key should be known to the SFTP (server), so they trust us when we set up the communication
30		-* A private key comes with a passphrase
	26	+There are two distinct ways of retrieving and storing the unique fingerprint of the SFTP in a "known hosts file". The first option is portal based and the second option is command line based. The preferred option is the portal based one. Do note that the first option only works if the SFTP is **publicly** accessible without any IP restrictions.
31	31
32		-If you are looking for some introductory reading into certificates, please check this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Securing Data Traffic.novice-securing-your-data-traffic-what-are-certificates.WebHome||target="blank"]].
	28	+=== 3.1 Known Hosts File Generation - Portal ===
33	33
34		-As the private key is yours, you can ask a trusted party to generate the key, or you could create it yourself. The latter part happens a lot when connecting to an SFTP. You could use a tool like PuttyGen to achieve this. As a result, you will have a keypair. The private key should be kept safely with you in eMagiz, and you need to share the public key with the SFTP server party. In this microlearning, I will not explain how PuttyGen works in detail. Instead, we will focus on the part in eMagiz. In eMagiz, we need to refer to the key file (linked under Resources), and we need to refer to the password we use to save our key file securely.
	30	+To configure the preferred option we start at the flow level in Create. Once the flow is opened please enter "Start Editing" mode and navigate to the Support object tab in the right panel. In here open the SFTP (caching) session factory that is used to connect to the SFTP.
35	35
36		-[[image:Main.Images.Microlearning.WebHome@intermediate-file-based-connectivity-sftp-security--private-key-config.png]]
	32	+[[image:Main.Images.Microlearning.WebHome@intermediate-file-based-connectivity-sftp-known-hosts--sftp-session-factory-start.png]]
37	37
38		-Note that the use of a password and a private key are mutually exclusive. So you need to either provide a password or a private key for authentication. In the help text provided by eMagiz, you can see how the reference to the key file should be made.
	34	+Once you see the configuration of the component please define a property for the known hosts field. This property will later on be used to generate and store the known hosts file while in Deploy.
39	39
40		-When you have configured these settings, you have finished the configuration in eMagiz. Now you could test whether the configuration is set up correctly between eMagiz and the SFTP. If this is not the case, eMagiz will notify you via the Manage phase, either as an error message or a log entry.
	36	+[[image:Main.Images.Microlearning.WebHome@intermediate-file-based-connectivity-sftp-known-hosts--sftp-session-known-hosts.png]]
41	41
42		-Using this setting gives the server the option to verify if the communication request came from eMagiz (or at least from the party that holds the private key of eMagiz). This is an additional security measure to ensure data integrity and quality.
	38	+When you are satisfied with the configuration you can save it, press "Stop editing", and create a new version of the flow. Now that we have a new version of the flow we navigate to the Deploy phase to trigger eMagiz to generate and store the known hosts file correctly on runtime level.
43	43
	40	+=== 3.2 Known Hosts File Generation - Command Line ===
	41	+
	42	+The secondary option, when there are IP restrictions, provides you with the option to execute several commands after gaining access to the correct server to generate the known hosts file. These steps are detailed below.
	43	+
	44	+* Gain access to the server in question from which you can reach the SFTP.
	45	+* Execute the following command (compatible with both Linux and Windows): {{code}}ssh-keyscan -p [port] [host] > [known-hosts target path]{{/code}}
	46	+** An example would be: {{code}}ssh-keyscan -p 22 localhost > C:\tmp\generated_known_hosts{{/code}}
	47	+* Navigate to the generated file and open it. The file should contain one or more lines in the format {{code}}hostname/ip key-type value
	48	+e.g. 127.0.0.1 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAICZPI5pQ6PSXgS4QOPsai2QjC2EcVjFejvUM5RMYOmwbwW{{/code}}
	49	+* Open eMagiz and navigate to the flow where the file is needed.
	50	+* Upload the known_hosts file as a flow resource, and click on the "eye" icon to see its unique name.
	51	+* Define a property for the known hosts field in the SFTP (caching) session factory.
	52	+** Provide a value for the property upon deploying the release that follows the following structure: {{code}}classpath:emagiz-resources/[filename]{{/code}}
	53	+
44	44	== 4. Key takeaways ==
45	45
46		-* Private key is unique per client
47		-* Private key should only be known to the client
48		-* Public key should be known to the SFTP (server), so they trust us when we set up the communication
49		-* A private key comes with a passphrase
	56	+* Each SFTP has a unique fingerprint that identifies the SFTP.
	57	+* To prevent a "man in the middle" attack, this fingerprint needs to be stored client side.
	58	+* There are two distinct methods to generate the known hosts file.
50	50
51	51	== 5. Suggested Additional Readings ==
52	52
53	53	If you are interested in this topic and want more information, please read the release notes provided by eMagiz. Furthermore, check out these links:
54	54
55		-* [[SFTP Outbound>>https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-outbound||target="blank"]]
	64	+* [[Known Hosts Files explained>>https://stackoverflow.com/questions/33243393/what-is-actually-in-known-hosts||target="blank"]]
56	56	* [[SFTP Session Factory>>https://docs.spring.io/spring-integration/docs/2.2.6.RELEASE/reference/html/sftp.html#sftp-session-factory||target="blank"]]
57		-* [[SFTP Authentication>>https://www.2brightsparks.com/resources/articles/sftp-authentication.html||target="blank"]]
58	58
59	59	)))((({{toc/}}))){{/container}}{{/container}}