From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 8C0C4C0015E for ; Tue, 25 Jul 2023 17:06:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1690304769; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=/qVLO/qtnKO1EPcrXxzAXfRrit5xUD+2hcrlwWNtFCw=; b=DiGH28VFvsR8kax9oCNx2Rcp8NL0mXgIGhqGgRKssCmt+IRabri5HKpAhH+9SmVOkksB/t GdwbhrWXDcdEY3bAEL+p7smq41ocdbuxlFPSsCdMwAiAedoD7Mswk4Ep9V9PbaYdmutixv +j57r8GPDR61EuFeblDNXVNcGeBPT9U= Received: from mimecast-mx02.redhat.com (66.187.233.73 [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-597-J69dXXTnOy6LNgMyTBmlKA-1; Tue, 25 Jul 2023 13:06:05 -0400 X-MC-Unique: J69dXXTnOy6LNgMyTBmlKA-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E06E32808E60; Tue, 25 Jul 2023 17:06:02 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id AC769492B01; Tue, 25 Jul 2023 17:05:59 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 611E319465B9; Tue, 25 Jul 2023 17:05:54 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id D21561946589 for ; Tue, 25 Jul 2023 17:05:52 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 9EF5AC2C856; Tue, 25 Jul 2023 17:05:52 +0000 (UTC) Received: from x2.localnet (unknown [10.22.9.133]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 701C6C2C7D3; Tue, 25 Jul 2023 17:05:52 +0000 (UTC) From: Steve Grubb To: Samuel Bahr Subject: Re: Cannot disable kernel's audit system via auditctl Date: Tue, 25 Jul 2023 13:05:51 -0400 Message-ID: <2241383.iZASKD2KPV@x2> Organization: Red Hat In-Reply-To: References: <2691760.mvXUDI8C0e@x2> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-BeenThere: linux-audit@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Audit Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-audit@redhat.com Errors-To: linux-audit-bounces@redhat.com Sender: "Linux-audit" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Monday, July 24, 2023 5:06:02 PM EDT Samuel Bahr wrote: > `auditctl -D` does not make it go away (outputs `No rules`). auditd isn't > running at all and this behavior is happening purely from the kernel. These > systems were never set to enabled 2 (locked). > > I went ahead and filed a Github issue for this thread: > https://github.com/linux-audit/audit-kernel/issues/146 > > The maintainer there suggested it's too difficult to debug due to eBPF > programs + AWS's modified kernel. I think there is data that could help decide where the problem might be. On one of the systems that is still logging, try running an event type report: aureport --start yesterday --event --summary -i This should identify what kind of event is being emitted. Based on that, it might point to where the problem is. > I've resigned to asking Red Canary to support eBPF mode with `audit=0` > kernel parameter in their Linux EDR. Let me know if you have any other > ideas. I'd say collecting summary information about what kind of events are being logged would be a good start. -Steve -- Linux-audit mailing list Linux-audit@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit