Your location：Home>虚拟化软件 视频会议>虚拟化软件

LiquidFiles

 

LiquidFiles

 

How do you Send a Large File using LiquidFiles?

 

LiquidFiles is a virtual appliance server you install in your environment. This is a typical deployment and a typical usage:

 

In this example, Jenny in marketing is sending a marketing brief to Joe at an advertising company they're working with for a new campaign. Since the files she needs to send are large, about 100 MB (100 MB is large in the context of email, LiquidFiles can send unlimited file sizes so 100 MB is not very large for LiquidFiles), and somewhat sensitive, email doesn't really work. Instead, she uses the company's installed LiquidFiles File transfer appliance.

  1. First, she visits https://securesend.company.com, the company's configured URL for their LiquidFiles appliance. Not that Jenny knows, but it's installed in the company's DMZ, behind the company's firewall. Once logged in with her AD username and password, she uploads the marketing brief, enters Joe's email address and writes a short message.
  2. An email is delivered to Joe with a link for him to download the marketing brief.
  3. When he clicks on the link, Joe is taken to the LiquidFiles server. When he's validated his email address to prove that it's really Joe, he downloads the files over a secure https connection. Joe does not have an account on the LiquidFiles server but using email validation can still be authenticated.
  4. When the download has completed, a download receipt is sent to Jenny, so that she knows that Joe has received the files.

 

How does it look?

This is how the main part of the interface looks when someone logs in to LiquidFiles to send a file.

 

  1. You can enter as many recipients as you need (hundreds...). Click on the CC and BCC button if you want to add CC or BCC addresses as well.
  2. Enter a subject line and a message just as you would in an email.
  3. To add files you can either drop files in the "Drop Files Here" section, add files using the "Add Files" button or select files you've already sent, so you don't have to re-upload that 20GB Cad drawing again to send to another recipient.
  4. You can select if the recipient needs to authenticate to access the message. If it's sensitive information, you want to require authentication. If the data is completely open, you may want to send without requiring authentication.
  5. You can select who has access to this message:
  1. The message expires, and the files will be deleted at this date.
  2. The message expires after this many downloads per recipient.
  3. Send a copy to myself (to store in your sent folder).
  4. A private message is when the body of the message is treated as sensitive and won't be copied to the recipient. You will also get a read receipt when someone's opened the message.
  5. If there are storage or admin set limits to how large files you can send, and any file type restrictions. LiquidFiles supports Unlimited Size Files, but you may want to set quotas for certain groups of users.

 

What happens when the recipient downloads a file?

One important aspect of sending large files securely is the logging of who downloaded what and when. LiquidFiles records not only who downloaded what and when, but also uses geo-location to track where the download was initiated, what operating system and browser was used and so on.

With LiquidFiles, you will always know what happened with your data.

 

Receive Large Files

Receiving Large Files can often be just as challenging as sending large files. To help facilitate Receiving Large Files Fast and Secure to your local users, LiquidFiles has many functions on offer:

 

Filedrops

A Filedrop is a permanent URL on your LiquidFiles server.

Filedrops are perfect for functions such as receiving Field Reports, Large Print Jobs, Tender Submissions, Technical Support files, ... We even have customers that use Filedrops to receive Job Applications.

When someone submits a Filedrop, the files are sent through to a pre-defined recipient. The support team will receive the support files, HR will receive job applications and so on.

 

User Filedrops

Similar to Filedrops above with the difference being that User Filedrops are pre-defined for your local users as a group.

 

When enabled, all your local users will get their own Filedrop that they can use. Many of our customers’ users add the link to their User Filedrop to their Email Signature.

 

File Requests

When you're expecting someone to send something to you, you can use LiquidFiles to send a File Request to someone.

 

The recipient of the File Request will get an email with a one-time link that they can click on and send the files. With a File Request, there's no To or From to fill in, we know that already so it's a very simple way for the recipient to just add the files requested, type a message and click send to respond to the File Request.

 

Send Files using the Regular Compose Message

LiquidFiles by default comes predefined with quite a few types of user groups, such as local users and external users. An external user is someone that can only send files to you. So if you're expecting someone to frequently send files to your organisation, you can create an account for them on your LiquidFiles system as an external user. This means that they can login and send files, and if your domain is @company.com, the external user can send something to joe.user@company.com but not to someone.else@external.com.

 

You can also create your own groups, for both local and external users, to further customize your requirements so that you can for instance define that some external users can only send Office Documents and others can send any file types. Or some external users can only send max 100MB files, while others can send 10GB at a time.

 

FTPdrops

In many organisations, there's many batch jobs and similar that uses legacy protocols such as FTP to send files periodically. If you want to standardize on LiquidFiles for all your file transfer needs in and out of your organization, you can setup LiquidFiles FTPdrops to be the target of these FTP file transfers. When a file is uploaded, LiquidFiles will perform it's usual Anti-Virus scan (and other type of scanning you may have configured), log and transfer the file onwards like a file received using a normal Filedrop.

 

FTPdrops supports FTP, FTP over SSL/TLS, SFTP and SCP.

 

Emaildrops

Emaildrops is similar to Filedrops or FTPdrops for email (regular SMTP Emails).

Emaildrops came to be because a customer had a procedure where they had many, many external brokers that filled out paper forms all over the country. When the form was filled in they would scan the form to a PDF in a multi-function printer and automatically email to a pre-defined email address. The company policy regarding regular emails was that everything needed to backed up for 7 years and they realized that Terabytes of these email backups was actually these one-time use PDF forms at about 5MB each that didn't really need to be backed up. So instead of sending these forms using email to their regular mail server, they sent it through LiquidFiles using an Emaildrop and in the process it saved them a lot of hassle and a fair bit of money.

 

Sharing Files & Folders with LiquidFiles

 

Often it's convenient to setup a place where you can share Files and Folders, for instance when working with a project and multiple people are contributing to the same project. Or just provide a convenient location to share organization documentation such as documentation, marketing materials, logo's and similar where only the marketing department can write to, and the entire organization can read the files.

 

Starting with LiquidFiles v3, File and Folder sharing is now part of the solution to facilitate this functionality. Specific Features regarding File and Folder sharing in LiquidFiles includes:

 

As you can see in the screenshot below, the File and Folder Sharing interface looks exactly as you expect from this functionality.

 

Your Files — Your Security

With LiquidFiles, you are in complete control over where your files are stored.

You can either deploy the application in your data center or in the Amazon EC2 cloud. The difference with almost all other options is that your sensitive corporate data is shared with other organizations and security is outside of your control. LiquidFiles is different and will match the security of your existing environment.

 

Encryption

LiquidFiles uses industry standard 256 bit AES encryption as default for all transfers. All cryptographic, randomization and token generation uses cryptographically strong OpenSSL functions to operate encryption and random number generation as opposed to often used default less secure functions in the operating system. This is particularly true for random number generators which is often the weak link in end to end cryptographic systems.

 

Authorization

Each message can be sent with the following different download permissions:

 

Local Users here refers to either a list of domains you've listed as being local, i.e. yourcompany.com. Or individual users that you've listed as local.

 

Authentication

LiquidFiles has very flexible Authentication mechanism that enables you to:

 

Auditing

 

Flexible Deployment

LiquidFiles can either be deployed either in your own data center or running in the Amazon EC2 cloud.

 

Local Data Centre deployment

The by far most common deployment. You have complete control over the installation, where the data is stored, and the fastest performance for your staff when sending files.

Typically LiquidFiles will be deployed right next to your mail server, in a public facing DMZ.

 

Amazon EC2 deployment

When you want the flexibility of cloud deployments, while still retaining complete control and security of your data, the Amazon EC2 version of LiquidFiles is perfect for you.

You can always move your license between any supported platform, as long as you only run one server at a time with the same license.

 

Compliance

 

By using LiquidFiles, you will be able to send large files securely within the organization, to customers, contractors, accountants, patients, and anyone else you need to communicate with securely.

 

It will also help you achieve Policy Compliance for Sarbanes-Oxley, HIPAA, PCI and other standards by encrypting sensitive data in transit, provide cryptographically strong random access keys for accessing transmitted data, and achieve non-repudiation with download receipts of who download what, from where (even by mapped locations) and at what time.

 

LiquidFiles has been deployed and deemed compliant in Sarbanes-Oxley, HIPAA and PCI environments. Please note though that even though these standards should provide a sort of simple tick-box security check (i.e. is this product HIPAA compliant?), in reality they are all generically worded and subject to interpretation. LiquidFiles will also specifically deal with technical controls, but very little in regards to administrative, policy and physical controls. In many cases it is also possible to provide mitigating controls if required, which is why it's important to get an auditor to verify the compliant status in each individual case.

 

Ease of Use, Integrations & API

 

One of the goals with LiquidFiles is that it should be easy to integrate into existing workflow. One example of this is the Outlook Plugin. Another example is the availability of the API.

 

The API enables external integration sending files with the LiquidFiles. Example use could include:

The API uses standard REST functions with an XML transport. You can code the API integrations using any modern language or framework such as C/Objective-C, Ruby, Perl, Java, .NET, ...

 

What some of our customers say...

 

“Perfect. I can't even begin to describe how pleased we are with your support and the product as a whole. We were referred to LiquidFiles by a partner of ours and we continue to recommend it every time someone asks us about it... you won’t be dissapointed.”

-- Ryan C

 

“Does exactly what it says. Plenty of options to configure it like you want. 2 minor support tickets were answered and fixed promptly. I would recommend this to anyone that needs secure transfer of large files.”

-- buzzra

 

LiquidFiles Features

 

Lots of Features, Still Easy to Use

This is a list of the Big ones and the Small and Important ones that shouldn't be overlooked either!

 

Overarching Design Principles

 

Sending and Downloading Files with Ease

 

Receiving Files as easy as possible

 

Filedrop pages static URLs for receiving files

A Filedrop page is a unique URL like https://liquidfiles.example.com/filedrop/status_reports, where the recipient is pre-set and the sender can be anyone.

 

File & Folder Sharing

Simple File & Folder sharing for internal and external projects, collaboration and sharing.

 

FileLinks links to individual files

A FileLink is a link to an individual file. It's perfect for when you don't know who the recipient is going to be, or for quickly post links to files in a forum, instant messager, post on an intranet and similar.

 

File Requests one time file receive

A File Request is a one-time file request users can send to any user. The recipient of the file request will get a one-time use link they can use to send files back to the requester.

 

Security protects you even when you don't realize it

 

Platform and Deployment

 

Branding and Localization

 

User and Group Management

 

API and plugins

北京哲想软件有限公司