Discussion Locked

Am I being Hacked?

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey does anybody out there recognize these events in Event Viewer Security log? Or am I being overly paranoid and what I'm looking at is the system itself accessing objects?
Event Type: Success Audit
Event Source: Security
Event Category: ObjectAccess
Event ID: 560
Date: 5/18/2002
Time: 1:38:00 AM
User: NT AUTHORITY\SYSTEM
Computer: WHITESTAR
Description:
Object Open:
Object Server: Security
Object Type: File
Object Name:
New Handle ID: 340
Operation ID: {0,600671}
Process ID: 804
Primary User Name: WHITESTAR$
Primary Domain: PROTECH
Primary Logon ID: (0x0,0x3E7)
Client User Name: -
Client Domain: -
Client Logon ID: -
Accesses DELETE
READ_CONTROL
WRITE_DAC
WRITE_OWNER
SYNCHRONIZE
ReadData (or ListDirectory)
WriteData (or AddFile)
AppendData (or AddSubdirectory or CreatePipeInstance)
ReadEA
WriteEA
Execute/Traverse
DeleteChild
ReadAttributes
WriteAttributesPrivileges -

4 replies

by maxwell edison

Success Audit:

An audited security access attempt that succeeds. For example, a user's successful attempt to log on the system will be logged as a Success Audit event.

Event Descriptions:

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/windows2000/en/server/help/sag_evmonevents_5.htm

To view more details about an event:

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/windows2000/en/server/help/sag_evmonevents_5.htm

(REMOVE SPACES fromthe pasted URLs.)

Maxwell

by gigelul

These events was generated by an enabled audit.
If you don't recognize:
-computer: WHITESTAR
-domain: PROTECH
then can be an issue.
But I see that:
-ClientUserName
-ClientDomain
-ClientLogonID
are empty. Normaly here must be some information if the audit was enabled for all users.

by shanghai sam

I don't think you're being hacked. it seems it's just the system log on reading the SAM database when you log on. If you really want to know if you're being hacked you need to audit the C:\WINN
repair folder where the SAM file is. To do that followthis:
1. Enable Success and Failure in Local Policies-Audit Policy.
2. right click th repair folder which is inside the WINNT folder and go to properties-security tab the Dis-elec the "allow inheritable permissions" then delete all the users and groups who have access to this folder leavingo only the local administrator account (it means only the amadministrator can access this folder)
3. Next click advanced then the auditing tab and add the "Everyone" group. This way you will be auditing everyone who try to access the repair folder. Of course only the local administrator user can access this folder so all the other attempts in event will be recorded as a failure . Also this is a good aywayo check for attempts originated inside the network such as employees or user trying to access this folder to get the system password. This procedure can also be applied to sensitive documents or important data to keep an eye on who is accessing it or try to access it

by jcmillenium

To UserDeleted;
Your answer was very helpful however when you stated setting the success and failure setting in Audit policy did you mean set all of them? There are 9 audit policies, wouldn't object access be the only policy to set and if you enable all of the audit policies won't you bog down your security log?

This discussion is closed to new replies.