Overview of PDF.co API Security Features
Security is important for us. We use SSL and TLS security and file encryption at rest to protect your data. You can also add user-controlled AES encryption and decryption for your data.
Our servers are hosted on the world-class infrastructure at Amazon AWS to keep your data safe and secure.
- Overview of PDF.co API Security Features
- PDF.co API Security Features
- Data Transmission
- Data Encryption
- Data Security
- Physical Security
- Security Frameworks
For Service Status page please visit https://status.pdf.co/
PDF.co API Security Features
PDF.co API security features:
- PDF.co application is hosted at world-class Amazon AWS infrastructure (please see below for the details);
- High availability cluster design includes servers in different regions with behind application balancers and automatic routers;
- Temporary files are stored on the cloud storage with a strong encryption at rest;
- API logs are saved for a user and and available for review by user
- API logs details visible to all:
- Datetime stamp
- PDF.co API endpoint address
- HTTP method
- HTTP status code
- Credits consumed
- Response Status code
API Logs details visible only to users
- Async Job ID
- Request Body and Parameters
- Response Body and Output Parameters
API Logs details automatically filtered, redacted and removed:
- Passwords, remote access usernames and passwords, user-controlled encryption parameters;
Special "Strict API logging" is available for working with a sensitive data.
- In this mode all
Responseare redacted completely and not visible even to account owners. In other words, input and output parameters are not saved even into API logs;
API logs retention:
- Pay as you Go and Subscription plans provide different log storage capacity. Please review Subscription Plans for more details.
Access to API logs, files, html templates, document parser templates
- API logs are available to account owners only;
- Users can open temporary access (for up to 48 hours or less ) via a special command requiring to explicitly allow temporary access. Access is auto-removed after 96 hours automatically or can be removed by user manually earlier;
Documents and data are processed in-memory except few functions listed below:
.pptxwhich are used as input);
.ppt/xwhich are used as input);
Crash reports generated during errors on servers are auto-redacted from input files and user identifiable information to contain only information about engine stack without specific user or specific input document information.
Servers are regularly auto-rotated and replaced with new clean server images;
Generated output files are securely stored, encrypted at rest and auto removed
- uploaded and output files are stored under highly randomized urls in private Amazon AWS S3 bucket (with encrypted at rest encryption enabled);
- links to output files are additionally signed using AWS S3 signed s3 links feature;
- files are encrypted at rest with
256-bit AESkeys while stored in the cloud storage;
- output links automatically expire in
1hour by default (can be decreased down to
1minute or increased up to
- uploaded and output files also can be explicitly removed using
- you can also leverage user-controlled data encryption parameters to encrypt content of output files automatically;
PDF.co provides built-in secure permanent file storage
- store documents, images, pdf templates and other files for re-use in API
- files from the storage are available via randomly generated file tokens
- available only for use inside PDF.co API via special
Password-protected documents support
Password protected PDF documents are supported for input:
passwordparameter to include password to open protected pdf file
Password protection support for output PDF documents
Password protection and security restrictions can be added to output PDF files generated or processed through the platform:
- PDF.co API provides
pdf/security/addendpoint that can enable built-in pdf documents protection too:
- disable or enable printing
- disable or enable copying of content
- add or remove user or owner password
- add or remove document permissions (printing, data extraction, merging)
- add digital signature (coming soon)
- additional user-controlled data encryption and decryption is available for automatic AES encryption and/or decryption of input/output file contents on byte level;
PDF.co can read links protected with HTTP authentication
httppasswordfor http based authentication (via
User Controlled Data Encryption (AES encryption) for input and output files
For additional security, the platform can decrypt input files on byte level and can encrypt output files on byte level with user controlled strong encryption (
Automatically encrypt output files with strong
Automatically decrypt input files previously encrypted with industry standard
Supported encryption algorithms:
256-bitAES encryption and decryption;
192-bitAES encryption and decryption;
128-bitAES encryption and decryption;
User-controlled encryption parameters are supported by all endpoints that read or generate files;
User controlled decryption for input files and encryption for output files can be used simultaneously within same API call. Please check this KB article for more details and sample parameters;
Allowed IP list
To restrict access to API and/or UI to a set of IP addresses only. Available through
Account - Security in PDF.co dashboard;
Single-sign on (SSO, SAML).
SSO mitigates compliance and security risks for organizations by giving businesses control over user authentication and user revocation via corporate-mandated tools;
History of Logins
The history of recent logins is available for review inside
API logs screen and includes
date and time every login to your account.
The availability of specific security features may vary depending on your subscription plan.
IP Addresses used by PDF.co Cloud
PDF.co Cloud is hosted on Amazon AWS infrastructure. Please see our KB article for more information about IP addresses and IP ranges used by AWS here.
How exactly PDF documents are processed by API in terms of security?
pdf/edit/add process for processing documents via our API follows these steps:
- Our API receives a request with an input link.
- The request is logged in the API logs for the account until "Strict API Logs" mode is enabled.
- The backend server processes the request.
- The backend server loads the source file from the provided URL into memory. Our own PDF engine parses the PDF in memory.
- The backend server updates the PDF in memory by adding text, filling out fields, and adding images.
- The backend server generates the final PDF and saves it into the non-public encrypted S3 bucket "pdf-temp-files" hosted on Amazon AWS, which is encrypted at rest by strong AES encryption.
- The PDF and related data are removed from server memory.
- The backend server uses Amazon AWS to generate a temporary signed link to access the output file for a limited - period of time, which is controlled via the "expiration" parameter.
- The backend server sends the output link back to the requester.
- The output link is also saved in the API logs until "Strict API Logs" mode is enabled.
PDF.co also provides an on-prem version of our API, which can work completely offline. For on-premise/Self-hosted version pricing, please visit this page or contact our support team.
Security is important for us. We use forced SSL and TLS security and file encryption at rest to protect your data. Our servers are hosted on the world-class infrastructure at Amazon AWS to keep your data safe and secure.
We do not use 3rd party API to process your documents, everything is processed on our servers only.
Your connections to application and API require Transport Layer Security Secure (TLS) and Secure Sockets Layer (SSL), cryptographic protocols designed to provide communications security over a computer network. Encryption is used to ensure a high level of security and privacy. When you upload documents and files, they are transmitted via encrypted connections.
Your permanent files are stored behind a firewall and authenticated against the sender’s session every time a request for that file is made. We enforce the use of industry best practices for the transmission of data to our platform (Transport Layer Security TLS) and data is stored in SOC 1 Type II, SOC 2 Type I, and ISO 27001 certified data centers at Amazon AWS cloud. Your documents are stored and encrypted at rest using AES 256-bit encryption.
When a file is generated by our server, it is stored under a randomized name to provide a unique link which is not possible to guess. Then the file is permanently removed after 1 hour by default. Generated files can also be removed right away using a
/file/delete API method at any time.
Servers and data are hosted and managed within Amazon’s secure data centers (US West 2 region) and utilize the Amazon Web Service (AWS) technology. Amazon continually manages risk and undergoes recurring assessments to ensure compliance with industry standards. Amazon’s data center operations have been accredited under:
- ISO 27001
- SOC 1 and SOC 2/SSAE 16/ISAE 3402 (Previously SAS 70 Type II)
- PCI Level 1
- FISMA Moderate
- Sarbanes-Oxley (SOX)
- AWS also provides an environment that enables businesses to comply with HIPAA regulations
PDF.co utilizes ISO 27001, FISMA, HIPAA certified data centers managed by Amazon. Amazon has many years of experience in designing, constructing, and operating large-scale data centers. This experience has been applied to the AWS platform and infrastructure. AWS data centers are housed in nondescript facilities, and critical facilities have extensive setback and military grade perimeter control berms as well as other natural boundary protection. Physical access is strictly controlled both at the perimeter and at building ingress points by professional security staff utilizing video surveillance, state-of-the-art intrusion detection systems, and other electronic means. Authorized staff must pass two-factor authentication no fewer than three times to access data center floors. All visitors and contractors are required to present identification and are signed in and continually escorted by authorized staff.
Amazon only provides data center access and information to employees who have a legitimate business need for such privileges. When an employee no longer has a business need for these privileges, his or her access is immediately revoked, even if they continue to be an employee of Amazon or Amazon Web Services. All physical and electronic access to data centers by Amazon employees is logged and audited routinely.
For additional information see: https://aws.amazon.com/security
SOC 2 compliance support (in work, expected in 2023):
* ByteScout, Inc. (d/b/a PDF.co) is in the process of implementation of SOC 2. [Contact us](https://support.bytescout.com/hc/en-us/requests/new) for more information * PDF.co runs on SOC 2 compliant data centers provided by Amazon AWS (see `Data Security and Physical Security` sections above;
HIPAA compliance support:
HIPAA compliance security features are available for
- Dedicated API Server (managed hosted private API server hosted on Amazon AWS);
- On-Prem API Server (self-hosted in your own private cloud or your company's infrastructure);
Document Encryption and Data Encryption support:
pdf/security/removeendpoints providing support for adding password to PDF, setting up security permissions.
- all endpoints include
passwordparameter for reading password protected pdf files;
- User-controlled data encryption (
AES 256) and AES decryption are available for auto-encrypting output files and auto-decrypting input files and documents. User-controlled data encryption is compatible with the user-controlled encryption settings in leading online platforms (such as SalesForce and others);
HIPAA compliance for PDF.co (cloud version): currently in work.
GDPR compliance support:
GDPR compliance features are available for
- Dedicated API Server (can be hosted in EU region of your choice)
- On-Prem API Server (hosted on your own server);
Local Data Privacy Requirements support:
Local Data Privacy Requirements support is available for
- Dedicated API Server (can be hosted in EU region of your choice)
- On-Prem API Server (hosted on your own server);
Credit Card Information
PDF.co does not store your credit card information. When you submit your credit card information, it is passed to our payments processor Stripe, a PCI Service Provider Level 1 service, or to FastSpring (BrightMarket LCC, USA), our authorized reseller.
Upon request, PDF.co will work to expunge all customer data and solely owned documents from our systems. You can always delete your account from your profile page. Contact us if you need assistance with data deletion.
last updated April 4, 2023