fuzzyfreak
asked on
Hack Attempts in my ISA Log - Should I be concerned?
After a little research, I am pretty sure these are normal and they do not appear to get onto my server. The logs show nothing further than the "cs-uri" column, where-as genuine entries do.
See attached for the latest ones, I have replaced my IP with "My IP Address" for security. This investigation was prompted by a recent worrying event log pasted below but this doesn't tie up with the logs -
Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12294
Date: 01/04/2010
Time: 23:09:25
User: Administrator
Computer: BENCOMMS
Description:
The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
ISA-Log.txt
See attached for the latest ones, I have replaced my IP with "My IP Address" for security. This investigation was prompted by a recent worrying event log pasted below but this doesn't tie up with the logs -
Event Type: Error
Event Source: SAM
Event Category: None
Event ID: 12294
Date: 01/04/2010
Time: 23:09:25
User: Administrator
Computer: BENCOMMS
Description:
The SAM database was unable to lockout the account of Administrator due to a resource error, such as a hard disk write failure (the specific error code is in the error data) . Accounts are locked after a certain number of bad passwords are provided so please consider resetting the password of the account mentioned above.
ISA-Log.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just throwing this out there:
As a rule of thumb, you should always change the default "administrator" ID to something other than "administrator". By leaving it at default, you give every script-kiddie 1/2 of your ID/PW combination.
As a rule of thumb, you should always change the default "administrator" ID to something other than "administrator". By leaving it at default, you give every script-kiddie 1/2 of your ID/PW combination.
ASKER
Yes, I totally agree but never been sure of the implications, particularly the impact on services that need a domain admin account. Is there an article that makes this clear?
Well, if you've setup services to logon using the DOMAIN/ADMINISTRATOR account, then renaming the account would mean having to go and change logon credentials for all those services.
You could easily setup a service account, make it a domain admin, and use the service account in the logon instead. Then once all the service logons have been updated (along with any scheduled task logons, etc) you should be able to rename the admin account.
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/RenameTheAdministratorAccount.html
http://www.computerperformance.co.uk/Litmus/security.htm
You could easily setup a service account, make it a domain admin, and use the service account in the logon instead. Then once all the service logons have been updated (along with any scheduled task logons, etc) you should be able to rename the admin account.
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/RenameTheAdministratorAccount.html
http://www.computerperformance.co.uk/Litmus/security.htm
ASKER
Event Type: Success Audit
Event Source: Security
Event Category: System Event
Event ID: 515
Date: 01/04/2010
Time: 23:09:06
User: NT AUTHORITY\SYSTEM
Computer: BENCOMMS
Description:
A trusted logon process has registered with the Local Security Authority. This logon process will be trusted to submit logon requests.
Logon Process Name: Winlogon\MSGina
I looked up this MSGina and it refers to the Ctrl Alt Del logon screen so not really sure what that tells me though I can assure you it wasn't physical.