Security Hub controls for Transfer Family
These AWS Security Hub controls evaluate the AWS Transfer Family service and resources.
These controls may not be available in all AWS Regions. For more information, see Availability of controls by Region.
[Transfer.1] AWS Transfer Family workflows should be tagged
Category: Identify > Inventory > Tagging
Severity: Low
Resource type:
AWS::Transfer::Workflow
AWS Config rule: tagged-transfer-workflow (custom Security Hub rule)
Schedule type: Change triggered
Parameters:
| Parameter | Description | Type | Allowed custom values | Security Hub default value |
|---|---|---|---|---|
requiredTagKeys
|
List of non-system tag keys that the evaluated resource must contain. Tag keys are case sensitive. | StringList | List of tags that meet AWS requirements |
No default value
|
This control checks whether an AWS Transfer Family workflow has tags with the specific keys defined in the parameter
requiredTagKeys. The control fails if the workflow doesn’t have any tag keys or if it doesn’t have all the keys specified in the
parameter requiredTagKeys. If the parameter requiredTagKeys isn't provided, the control only checks for the existence
of a tag key and fails if the workflow isn't tagged with any key. System tags, which are automatically applied and begin with aws:,
are ignored.
A tag is a label that you assign to an AWS resource, and it consists of a key and an optional value. You can create tags to categorize resources by purpose, owner, environment, or other criteria. Tags can help you identify, organize, search for, and filter resources. Tagging also helps you track accountable resource owners for actions and notifications. When you use tagging, you can implement attribute-based access control (ABAC) as an authorization strategy, which defines permissions based on tags. You can attach tags to IAM entities (users or roles) and to AWS resources. You can create a single ABAC policy or a separate set of policies for your IAM principals. You can design these ABAC policies to allow operations when the principal's tag matches the resource tag. For more information, see What is ABAC for AWS? in the IAM User Guide.
Note
Don’t add personally identifiable information (PII) or other confidential or sensitive information in tags. Tags are accessible to many AWS services, including AWS Billing. For more tagging best practices, see Tagging your AWS resources in the AWS General Reference.
Remediation
To add tags to a Transfer Family workflow (console)
Open the AWS Transfer Family console.
On the navigation pane, choose Workflows. Then, select the workflow that you want to tag.
Choose Manage tags, and add the tags.
[Transfer.2] Transfer Family servers should not use FTP protocol for endpoint connection
Related requirements: NIST.800-53.r5 CM-7, NIST.800-53.r5 IA-5, NIST.800-53.r5 SC-8, PCI DSS v4.0.1/4.2.1
Category: Protect > Data Protection > Encryption of data-in-transit
Severity: Medium
Resource type:
AWS::Transfer::Server
AWS Config rule:
transfer-family-server-no-ftp
Schedule type: Periodic
Parameters: None
This control checks whether an AWS Transfer Family server uses a protocol other than FTP for endpoint connection. The control fails if the server uses FTP protocol for a client to connect to the server's endpoint.
FTP (File Transfer Protocol) establishes the endpoint connection through unencrypted channels, leaving data sent over these channels vulnerable to interception. Using SFTP (SSH File Transfer Protocol), FTPS (File Transfer Protocol Secure), or AS2 (Applicability Statement 2) offers an extra layer of security by encrypting your data in transit and can be used to help prevent potential attackers from using person-in-the-middle or similar attacks to eavesdrop on or manipulate network traffic.
Remediation
To modify the protocol for a Transfer Family server, see Edit the file transfer protocols in the AWS Transfer Family User Guide.
