大网数据广告活动
服务器运维问答

How to keep access keys safe in the event of a compromised server?

· 52CE 我爱测

What's the best strategy to keeping access tokens secure in the event of a compromised server? Let's say I have a Linux web server to which I regularly ssh into. There is a variety of critical access tokens stored on this server …

问题原文

原帖链接 · Sergey · CC BY-SA 3.0

What's the best strategy to keeping access tokens secure in the event of a compromised server?

Let's say I have a Linux web server to which I regularly ssh into. There is a variety of critical access tokens stored on this server (e.g. encryption keys, Amazon S3 for backups, etc). If an attacker can ssh into the server, what's the best strategy to prevent them from reading the keys?

已采纳解答

原帖链接 · Jeff Ferland · CC BY-SA 3.0

It's pretty hard to keep keys from being read. Mandatory access control on your daemons using AppArmor or SELinux will kick up the ability to limit read access.

Making use of software like Vault kicks it up a notch. Like the temporary credential system given by Amazon's STS, this can be applied to any backend you write a module for a few exist thus creating temporary and easily revocable credentials. If written directly into your app, this will keep passwords outside of configuration files.

You can use an authentication backend such as the App ID one or if you have hardware, get super fancy and write a TPM based one.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-02-09)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。