5 replaced http://serverfault.com/ with https://serverfault.com/
source | link

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-teamhttps://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

Best Practice: “One per-user ssh key” or “multiple per-host ssh keys”

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

Best Practice: “One per-user ssh key” or “multiple per-host ssh keys”

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see https://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

Best Practice: “One per-user ssh key” or “multiple per-host ssh keys”

4 replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
source | link

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

http://security.stackexchange.com/questions/18926/best-practice-one-per-user-ssh-key-or-multiple-per-host-ssh-keysBest Practice: “One per-user ssh key” or “multiple per-host ssh keys”

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

http://security.stackexchange.com/questions/18926/best-practice-one-per-user-ssh-key-or-multiple-per-host-ssh-keys

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

Best Practice: “One per-user ssh key” or “multiple per-host ssh keys”

3 added 125 characters in body
source | link

Since your shop now has maybe 80 employeesdoubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing (and/ access management - what if you need to quickly deauthorize a user?).  

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

http://security.stackexchange.com/questions/18926/best-practice-one-per-user-ssh-key-or-multiple-per-host-ssh-keys

Since your shop now has maybe 80 employees this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing (and access management - what if you need to quickly deauthorize a user?).  

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

Since your shop has doubled in headcount this increases the risk that someone will unintentionally or intentionally mismanage one or more SSH keys. Using SSH keys without going through LDAP creates the vulnerability that someone can, for example, make a connection to the system account and pull all the cardholder data out of your database, all as an authorized user and subverting auditing / access management.

See 2.3, 3.6, 8.1.

Also see http://serverfault.com/questions/471753/what-are-best-practices-for-managing-ssh-keys-in-a-team

and

http://security.stackexchange.com/questions/18926/best-practice-one-per-user-ssh-key-or-multiple-per-host-ssh-keys

2 added 108 characters in body
source | link
1
source | link