Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Communication between the agent and the Deep Security Manager

    • Updated:
    • 13 Aug 2013
    • Product/Version:
    • Deep Security as a Service 1.All
    • Platform:
    • CentOS 6 32-bit
    • CentOS 6 64-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 5 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • Linux - SuSE 10 64-bit
    • Linux - SuSE 11
    • Linux - SuSE 11 64-bit
    • Ubuntu 10.04 64-bit
    • Ubuntu 12.04 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2008 Server R2
    • Windows 2008 Server R2 with Hyper-V(TM)
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows 8 32-bit
    • Windows 8 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary
Learn more about how the Deep Security agent communicates with the Manager.
Details
Public
The agent communicates to using the following addresses:
  • agents.deepsecurity.trendmicro.com:443
  • relay.deepsecurity.trendmicro.com:443
This configuration is easy to implement for your instances in Amazon EC2 or inside a Virtual Private Cloud (VPC). For EC2 instances, you don’t need to to do anything since all outbound communications in EC2 are permitted and agents will work by default.
Within a VPC, you must enable an outbound route through an internet gateway. You must also add a rule to your security group to allow outbound communications for TCP over port 443. Most configurations will benefit from a rule that allows TCP over port 443 to address block 0.0.0.0/0 (everywhere). But if your instances are in us-east-1, you can restrict outbound 443 to Amazon Web Services (AWS) security group 147995105371/sg-958cdcfd.
Alternative communications
Deep Security as a Service also supports manager-initiated communications. In this case, the service calls your agent in order to perform various tasks.
We strongly recommend using agent-initiated communications as it is simpler to setup and maintain in the public cloud.
If you do wish to use manager-initiated communications you will need the following to allow inbound communications via TCP on port 4118 (the port the agent listens on) from either AWS security group 147995105371/sg-958cdcfd (if you’re in us-east-1) or CIDR block (54.221.196.0/24).
This requirement is in addition to all of the above agent-initiated communications requirements.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1098565
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.