Secure Email/File Transfer Service
To order or inquire about this service, please contact the NIH IT Service Desk.
Service Hours: 24 hours a day, 7 days a week
The Secure Email/File Transfer Service allows NIH users and customers to send large documents securely and confidentially over a secure socket layer (SSL)/encrypted connection.
To comply with the Federal Information and Security Management Act (FISMA) and continuously improve the security practices used at NIH, CIT has added an alternative method to the existing Public Key Infrastructure (PKI) encryption methods, called the Secure Email/File Transfer Service (SEFT).
This service allows NIH users to send, and its customers to receive, emails securely on an SSL/encrypted connection with or without large documents. Using the Secure Email/File Transfer Service ensures the protection of personally identifiable information (PII) and thoroughly secures all data and information being sent via email. SEFT also offers a level of non-repudiation and tracks correspondence history.
All NIH users are preregistered to receive deliveries through this service. To register to send email or large files using this service, please visit the Register for Secure Email link in the More Info box to the right.
Customer Benefits
This service helps NIH staff protect PII by providing a highly secure, PKI-less way to transfer large files. Because SEFT tracks correspondence history, customers can also have a record of their secure messages.
Customer Market
This service is available to all NIH ICs. Please note, the NIH Clinical Center has a dedicated instance of SEFT. Please see your ITPro for further information.
Frequently Asked Questions
Q: Which Secure Email option should I use – Public Key Infrastructure (PKI) or Secure Email/File Transfer Service (SEFT)?
A: If you need to send someone large files securely, you should use SEFT. SEFT uses a secure socket layer (SSL)/encrypted connection, offering a highly secure way to send very large files and attachments. As an added benefit, using SEFT does not require either the sender or the receiver of your message to have a PKI certificate.
Up to Top
