TCP Timestamps Information Disclosure on EKS Nodes

0

One of our compliance we found the recommendation To disable TCP timestamps on linux add the line using 'net.ipv4.tcp_timestamps = 0' to /etc/sysctl.conf. Execute 'sysctl -p' to apply the settings at runtime this is inlined with -

  • The remote host implements TCP timestamps, as defined by RFC1323/RFC7323.

Please guide how to achieve this ?

Ganesh
已提问 5 个月前771 查看次数
1 回答
0

Hi,

It depends on how you configure your EKS Nodes. It could be managed node groups, self-managed node groups or even EC2 instances added by the Karpenter to your cluster.

Anyway, you can create your own AMI images with the above changes, check if Bottlerocket has this enforcement enabled and switch to it or do the update via the UserData.

profile picture
专家
已回答 5 个月前
  • ok, But is there any consequences if we setup 'net.ipv4.tcp_timestamps = 0' in our EKS nodes ? any performance issue we might face ? we want to fix this, without breaking our Cluster performance
    ==> The remote host implements TCP timestamps, as defined by RFC1323/RFC7323.

  • Based on the information available about this feature, it can impact network performance and stability on the high load. Only you can test how it will impact your specific workload. I would assess the risks you have when it's enabled (I guess it's fingerprinting by the timestamp) and if it impacts your security at all.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则