Hey Guys,
CCI-001459 requires that temp accounts be terminated after a organizationally defined period of time. Right now we don't have a check/control that implements that.
I'd like to add prose that recommends that -ALL- accounts be locked after 60 (or 90... or 120..) days of inactivity. This would allow us to automatically meet CCI-001459 and enforces that inactive accounts should (eventually and automatically) be frozen.
Thoughts? My thinking is that 90 days of inactivity is a good number.
-Shawn
On 4/25/12 3:18 PM, Shawn Wells wrote:
Hey Guys,
CCI-001459 requires that temp accounts be terminated after aorganizationally defined period of time. Right now we don't have a check/control that implements that.
I'd like to add prose that recommends that -ALL- accounts belocked after 60 (or 90... or 120..) days of inactivity. This would allow us to automatically meet CCI-001459 and enforces that inactive accounts should (eventually and automatically) be frozen.
Thoughts? My thinking is that 90 days of inactivity is a good number.
Sitting in a room with Willy Santos, and he just brought up a good point. This really should be broken into 2 rules:
#1: All accounts should be disabled after 90 days inactivity
#2: Temp accounts need to be chage'd to $creationDate+90 days (procedurally). We could potentially identify temp accounts by suggesting they all be created within a specific UID range, then we can just chage on all UIDs within that range to verify temp accounts do not exceed 90 days - This could be a problem if account is "extended," we'll need to think through this...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/25/2012 01:22 PM, Shawn Wells wrote:
On 4/25/12 3:18 PM, Shawn Wells wrote:
Hey Guys,
CCI-001459 requires that temp accounts be terminated after a organizationally defined period of time. Right now we don't have a check/control that implements that.
I'd like to add prose that recommends that -ALL- accounts be locked after 60 (or 90... or 120..) days of inactivity. This would allow us to automatically meet CCI-001459 and enforces that inactive accounts should (eventually and automatically) be frozen.
Thoughts? My thinking is that 90 days of inactivity is a good number.
Sitting in a room with Willy Santos, and he just brought up a good point. This really should be broken into 2 rules:
#1: All accounts should be disabled after 90 days inactivity
How do you measure activity? login? checked email? logged in via ftp? Not all accounts are used to login. Also what happens if you use central admin like ldap/etc.
#2: Temp accounts need to be chage'd to $creationDate+90 days (procedurally). We could potentially identify temp accounts by suggesting they all be created within a specific UID range, then we can just chage on all UIDs within that range to verify temp accounts do not exceed 90 days - This could be a problem if account is "extended," we'll need to think through this...
Shouldn't they have created the temp account with an expiry date?
adduser - -e, --expiredate EXPIRE_DATE The date on which the user account will be disabled. The date is specified in the format YYYY-MM-DD.
or use usermod with the same option to auto expire the account at date X?
_______________________________________________ scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/scap-security-guide
- -- Kurt Seifried Red Hat Security Response Team (SRT) PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
Shawn,
90 days seems like a reasonable number.
R, -Joe
From: Shawn Wells shawn@redhat.com To: scap-security-guide@lists.fedorahosted.org Sent: Wednesday, April 25, 2012 3:18 PM Subject: Seeking Input: CCI-001459 Remediation - Temp Account Termination
Hey Guys,
CCI-001459 requires that temp accounts be terminated after a organizationally defined period of time. Right now we don't have a check/control that implements that.
I'd like to add prose that recommends that -ALL- accounts be locked after 60 (or 90... or 120..) days of inactivity. This would allow us to automatically meet CCI-001459 and enforces that inactive accounts should (eventually and automatically) be frozen.
Thoughts? My thinking is that 90 days of inactivity is a good number.
-Shawn _______________________________________________ scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/scap-security-guide
Agreed. I'll use that value unless someone screams.
-Shawn
On 4/25/12 3:43 PM, Joe Wulf wrote:
Shawn,
90 days seems like a reasonable number.
R, -Joe
------------------------------------------------------------------------ *From:* Shawn Wells <shawn@redhat.com> *To:* scap-security-guide@lists.fedorahosted.org *Sent:* Wednesday, April 25, 2012 3:18 PM *Subject:* Seeking Input: CCI-001459 Remediation - Temp Account Termination Hey Guys, CCI-001459 requires that temp accounts be terminated after a organizationally defined period of time. Right now we don't have a check/control that implements that. I'd like to add prose that recommends that -ALL- accounts be locked after 60 (or 90... or 120..) days of inactivity. This would allow us to automatically meet CCI-001459 and enforces that inactive accounts should (eventually and automatically) be frozen. Thoughts? My thinking is that 90 days of inactivity is a good number. -Shawn _______________________________________________ scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org <mailto:scap-security-guide@lists.fedorahosted.org> https://fedorahosted.org/mailman/listinfo/scap-security-guide
scap-security-guide@lists.fedorahosted.org