L
Leoš Junek
Hello,
I am using Windows Server 2012 R2. There I am facing an unwanted Windows Security Audit log entry that comes with Oracle 11gR2 connect from one database on Windows server No.1 to another Oracle 11gR2 database running on another Windows Server. Database link is used. The connection from database to database is successfull, no errors, however every connect raise an entry in Windows Event Logs.
Can I exlude particular event with specific network source and crendetials from logging? It´s false positive. I do not want this error to occur in my Event log. Is it possible to persuade Windows not to log it?
I am not interested in filtering Event log in Event Log viewer. The logs are collected and processed automatically with external tool.
Below an example of logged event is provided.
Hope someone can tell whether it is possible or not due to security reasons.
Leos
=======================
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 2. 12. 2019 9:13:58
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: some_name.domain.com
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: SOMEACCOUNT$
Account Domain: SOMEDOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: SOMEWRKSTATNAME
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
1.0
Continue reading...
I am using Windows Server 2012 R2. There I am facing an unwanted Windows Security Audit log entry that comes with Oracle 11gR2 connect from one database on Windows server No.1 to another Oracle 11gR2 database running on another Windows Server. Database link is used. The connection from database to database is successfull, no errors, however every connect raise an entry in Windows Event Logs.
Can I exlude particular event with specific network source and crendetials from logging? It´s false positive. I do not want this error to occur in my Event log. Is it possible to persuade Windows not to log it?
I am not interested in filtering Event log in Event Log viewer. The logs are collected and processed automatically with external tool.
Below an example of logged event is provided.
Hope someone can tell whether it is possible or not due to security reasons.
Leos
=======================
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 2. 12. 2019 9:13:58
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: some_name.domain.com
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: SOMEACCOUNT$
Account Domain: SOMEDOMAIN
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: SOMEWRKSTATNAME
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
1.0
Continue reading...