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
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.

Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Kruger_monkeyConnect With a Mentor Commented:
It's difficult to say for sure, but it looks like ISA is stopping the attempts.  however the event log entry clearly indicates that at some stage someone did indeed try and brute force the administrator account.  

When you review your security log, do you get a lot of failure attempts?

To be safe I would review all of you security applications.  General practice block everything and then open only what is needed.  Don't mean to be trivial, just covering bases.  You will probably find quite a number of attempts like that, but that's what ISA/firewalls etc are tehre for.  They can keep on knocking....

Review the security log, filter for failures and then go by that.  If you have an excessive amount of failures, definately review all of your security, if not then you are probably ok.
fuzzyfreakAuthor Commented:
hi, thanks very much for your response.  I should have mentioned that I had already scrutinised the security log and though nothing matched the exact time, this was happening close to it -

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
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.
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.  
fuzzyfreakAuthor Commented:
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.

All Courses

From novice to tech pro — start learning today.