5 tips to achieve minimum security for FTP

[tatsu_section bg_color= “” bg_image= “” bg_repeat= “no-repeat” bg_attachment= “scroll” bg_position= “top left” bg_size= “cover” bg_animation= “none” padding= ‘{“d”:”15px 0px 15px 0px”}’ margin= “0px 0px 0px 0px” border= “0px 0px 0px 0px” border_color= “” bg_video= “0” bg_video_mp4_src= “” bg_video_ogg_src= “” bg_video_webm_src= “” bg_overlay= “0” overlay_color= “” full_screen= “0” section_id= “” section_class= “” section_title= “” offset_section= “” offset_value= “0” full_screen_header_scheme= “background–dark” hide_in= “0” key= “fu02k8rgp21a6wc8”][tatsu_row full_width= “0” no_margin_bottom= “0” equal_height_columns= “0” gutter= “medium” column_spacing= “” fullscreen_cols= “0” swap_cols= “0” row_id= “” row_class= “” hide_in= “0” layout= “1/1” key= “fu02k8rgt16a6ebg”][tatsu_column bg_color= “” bg_image= “” bg_repeat= “no-repeat” bg_attachment= “scroll” bg_position= ‘{“d”:”top left”}’ bg_size= ‘{“d”:”cover”}’ padding= ‘{“d”:”0px 0px 0px 0px”}’ custom_margin= “0” margin= ‘{“d”:”0px 0px 0px 0px”}’ border= ‘{“d”:”0px 0px 0px 0px”}’ border_color= “” enable_box_shadow= “0” box_shadow_custom= “0 0 15px 0 rgba(198,202,202,0.4)” bg_video= “0” bg_video_mp4_src= “” bg_video_ogg_src= “” bg_video_webm_src= “” bg_overlay= “0” overlay_color= “” animate_overlay= “none” link_overlay= “” vertical_align= “none” column_offset= “0” offset= “0px 0px” z_index= “0” column_parallax= “0” animate= “0” animation_type= “fadeIn” animation_delay= “0” col_id= “” column_class= “” hide_in= “0” layout= “1/1” key= “fu02k8rgwm69ya1f”][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “fu02k8rh042cbnhm”]FTP, or File Transfer Protocol, was invented back in 1971 and long before ‘the internet’. It’s a standard network protocol that is built on a client-server architecture model that was developed for the transfer of files between a client and a server on a network. When FTP was developed, security was not in front of the line: authentication (user and password) and content are, for example, not encrypted. Clearly, that is the safest way to approach data transfer. Therefore, for secure transmission, FTP is often secured with SSL/TLS (FTPS) or replaced with SSH File Transfer Protocol (SFTP). Here, the content and the authentication process are encrypted and thus secured.

Given FTP is ‘free’ it was also widely adopted by businesses in the past. Today, many businesses still use FTP to exchange files with contractors, customers, etc. Where FTP software might be free, and cheap storage can be used in-house or in the public cloud, the consequences of a lack of security can be very, very vast.

We have 5 tips for companies that are still doing FTP today to increase protection to a ‘basic’ level:

1. Disable standard FTP and move to FTPS and/or SFTP: in the 21^st century, using a solution without decent privacy and integrity means putting the door wide open for hackers to access and modify your data.
2. Use the most recent encryption: if you’re already running FTPS or SFTP, make sure that you are using a recent encryption cypher solution such as AES. Don’t rely on old solutions like Blowfish or DES which can be easily hacked
3. Implement IP black- and whitelists: an IP blacklist denies a range of IP addresses from accessing the system, either temporarily or permanently. For example, you may want to block certain countries from access. This can also protect you (partially) from distributed DoS attacks
4. Use an FTP Gateway: typically, FTP servers used to be placed in the DMZ. Doing so limits the risks or exposure to the private network. However, given the DMZ is facing the public internet, it is also a segment that is very vulnerable to attack. Therefore, FTP gateways or reverse proxies can be used, as they offer a special control channel into the private network
5. Implement file and folder security: contractors, customers, employees, etc. should only have access to data they are allowed to see

Clearly, adding the (still) basic security layers increases the complexity for the admin, and will increase the cost of the setup. But let’s not forget the end-user impact. They will very often still need to install and setup a local FTP client. This becomes especially tricky (and support-intensive!) when the users are spread across many contractors and customers.

Let’s face it, FTP (even FTPS or SFTP) are not giving businesses the required level of protection, ease-of-use or manageability. Above the surface they are cheap (or free), but below the surface a whole range of risks and costs arise.

Awingu can be the modern alternative to FTP. Awingu is a browser-based “Unified Workspace” solution. It gives access to apps and files from a browser. Architecturally, Awingu is a virtual appliance that acts as a gateway on top of a WebDAV or CIFS file share (something you probably already have in-house).

Awingu will give users access to documents, the ability to download or upload, and even the ability to ‘share’ documents. All of this happens within the framework of a browser of your choice. That is nice and easy for the admin: he or she doesn’t need to manage anything on the end-user’s device.

[/tatsu_text][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “HyEYFtHr7”]

‘Files’ section in the Awingu workspace: access, download, upload or share documents

[/tatsu_text][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “B1dz9tBBQ”]

In terms of security, Awingu will add a whole lot: authentication runs via the built-in multi-factor authentication solution, and everything is encrypted and runs in HTTPS. The access rights in Active Directory and the file server will apply, so there’s no need to set up a separate rights management. Finally, everything is fully audited and enriched with anomaly detection to assure compliancy (e.g. for GDPR purposes).

[/tatsu_text][tatsu_inner_row no_margin_bottom= “0” equal_height_columns= “0” gutter= “medium” column_spacing= “px” swap_cols= “0” row_id= “” row_class= “” hide_in= “0” layout= “1/2+1/2” key= “BJeBr9tSBQ”][tatsu_inner_column bg_color= “” bg_image= “” bg_repeat= “no-repeat” bg_attachment= “scroll” bg_position= “top left” bg_size= “cover” padding= ‘{“d”:”0px 0px 0px 0px”}’ custom_margin= “0” margin= ‘{“d”:”0px 0px 0px 0px”}’ border= ‘{“d”:”0px 0px 0px 0px”}’ border_color= “” enable_box_shadow= “0” box_shadow_custom= “0 0 15px 0 rgba(198,202,202,0.4)” bg_video= “0” bg_video_mp4_src= “” bg_video_ogg_src= “” bg_video_webm_src= “” bg_overlay= “0” overlay_color= “” animate_overlay= “none” link_overlay= “” vertical_align= “none” column_offset= “0” offset= “0px 0px” z_index= “0” column_parallax= “0” animate= “0” animation_type= “fadeIn” animation_delay= “0” col_id= “” column_class= “” hide_in= “0” layout= “1/2” key= “ryPScYrHX”][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “H1jr5tBS7”]

Use Awingu’s built-in ‘One Time Password’ solution together with
Google Authenticator for secure authentication

[/tatsu_text][/tatsu_inner_column][tatsu_inner_column bg_color= “” bg_image= “” bg_repeat= “no-repeat” bg_attachment= “scroll” bg_position= “top left” bg_size= “cover” padding= ‘{“d”:”0px 0px 0px 0px”}’ custom_margin= “0” margin= ‘{“d”:”0px 0px 0px 0px”}’ border= ‘{“d”:”0px 0px 0px 0px”}’ border_color= “” enable_box_shadow= “0” box_shadow_custom= “0 0 15px 0 rgba(198,202,202,0.4)” bg_video= “0” bg_video_mp4_src= “” bg_video_ogg_src= “” bg_video_webm_src= “” bg_overlay= “0” overlay_color= “” animate_overlay= “none” link_overlay= “” vertical_align= “none” column_offset= “0” offset= “0px 0px” z_index= “0” column_parallax= “0” animate= “0” animation_type= “fadeIn” animation_delay= “0” col_id= “” column_class= “” hide_in= “0” layout= “1/2” key= “ByxwH9tHBQ”][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “BkFUctHBQ”]

Use Awingu’s built-in usage audit log gives full insight into who opened, deleted, uploaded, etc. what document and more

[/tatsu_text][/tatsu_inner_column][/tatsu_inner_row][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “r17WsYHS7”]

Oh, and we almost forget about the coolest thing: Awingu is a ‘workspace’. This means that you don’t need to limit yourself to files. You can run your legacy Windows, Linux or web applications and desktops in that same browser-based workspace!

[/tatsu_text][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “HkmVjKBr7”]

Run applications and desktops in your browser with Awingu

[/tatsu_text][tatsu_text max_width= ‘{“d”:”100″}’ wrap_alignment= “center” animate= “” animation_type= “fadeIn” animation_delay= “0” key= “HkMOjtrHQ”]

If you are curious about how Awingu can help your company in increasing IT security whilst enabling your workforce, check out Awingu.com or book a free demo with us!

[/tatsu_text][/tatsu_column][/tatsu_row][/tatsu_section]