1 Reply Latest reply: Jul 31, 2018 3:55 AM by Bala Bhaskar RSS

    Why Windows Event log detects Audit Failure entries when logging to Qlik Senes Hub

    Yukiko Sasamoto

      Request:

      Please advise if following detections can be ignored or security concerns.

       

      Tested Environment:

      - Qlik Sense (Nov 2017)

      - Qlik Sense (Feb 2018)

      - Qlik Sense (June 2018)

       

      How to re-produce the issue:

      1. Open Qlik Sense Hub
      2. Login
      3. Go to Windows EventView > Security, check the time when access to Hub you will see entry: Audit Failure.

       

      Client expressed their most concerns about Kerberos detection.

      Please note "Kerberos" settings under QMC > Proxies is disabled for reported client.

       

      Sample Entry

      =========================

      An account failed to log on.

       

      Subject:

          Security ID:        SYSTEM

          Account Name:        QLIKSERVER1$

          Account Domain:        DOMAIN

          Logon ID:        0x3E7

       

      Logon Type:            3

       

      Account For Which Logon Failed:

          Security ID:        NULL SID

          Account Name:       

          Account Domain:       

       

      Failure Information:

          Failure Reason:        Unknown user name or bad password.

          Status:            0xC000006D

          Sub Status:        0xC0000064

       

      Process Information:

          Caller Process ID:    0x1dc

          Caller Process Name:    C:\Windows\System32\lsass.exe

       

      Network Information:

          Workstation Name:    QLIKSERVER1

          Source Network Address:    -

          Source Port:        -

       

      Detailed Authentication Information:

          Logon Process:        Schannel

          Authentication Package:    Kerberos

          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.

      =========================

        • Re: Why Windows Event log detects Audit Failure entries when logging to Qlik Senes Hub
          Bala Bhaskar

          May be this is because of AD Group:

           

          If your AD connection is setup correctly and working then the first time that a user hits your URL they will be prompted to login with their AD credentials.  If successful, then an account is created in QLIK.  If you have a security rule created then a token will be automatically allocated to them.

           

          From that point on they can login and see whatever parts of the HUB they have access to based on security rules.

           

          The fact that their user account shows up in the QMC would lead me to believe that they successfully logged in.

           

          Check this thread:

          Active Directory users cannot login

           

          Or else, try to reinstall Qlik Sense and changing the user that start the services, it may helps.