Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Service Account Pswd Mgt |
|---|---|
| Date: | Fri, 6 Jan 2006 12:06:07 -0000 |
Hi Kathy, We've found that many companies have a 30 or 90 day password change policy on service accounts where possible, and for those situations where vendors provide applications where passwords can not be changed easily password alterations are usually performed when the software is reinstalled or upgraded. We produce a product called the Enterprise Password Safe which is in use by many companies to manage all types accounts. If you'd like to take a look the details are at; http://www.argosytelcrest.com/enterprise_password_safe.html If you want more information about our product please email me off the list. Thanks, Al Sutton Argosy TelCrest www.argosytelcrest.com -----Original Message----- From: kathy.kirk@prudential.com [mailto:kathy.kirk@prudential.com] Sent: 05 January 2006 21:50 To: security-management@securityfocus.com Subject: Service Account Pswd Mgt I've been asked how managing service accounts works in other organizations. What is your policy for changing Service Account passwords? Is it based on an event (e.g., administrator leaves the company) and or a time requirement (e.g., every 90 days). If your organization does change Service Account passwords, is it consistent across the organization? How do you enforce your policy? By Service Account, I'm referring to system IDs used to perform backups, automate FTPs, run applications, jobs, scripts, etc. thanks, kathy -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.14/222 - Release Date: 05/01/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.14/222 - Release Date: 05/01/2006
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Research Help, sukh . gill1 |
|---|---|
| Next by Date: | RE: Service Account Pswd Mgt, Alex Bermudez |
| Previous by Thread: | Service Account Pswd Mgt, kathy . kirk |
| Next by Thread: | RE: Service Account Pswd Mgt, Alex Bermudez |
| Indexes: | [Date] [Thread] [Top] [All Lists] |