Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1376507

Summary:	[RFE] Monitoring atypical system usage
Product:	Red Hat Enterprise Linux 7	Reporter:	Steve Grubb <sgrubb>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WORKSFORME	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	dpal, jhrozek, pkis, sgallagh, sgrubb
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-22 08:55:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steve Grubb 2016-09-15 15:36:08 UTC

Description of problem:
pam_access and pam_time can send audit events when blocking access due to policies violations. There is a new requirement in SP 800-53, AC-2(12) which asks for :

The organization:
(a) Monitors information system accounts for [Assignment: organization-defined atypical use]; and
(b) Reports atypical usage of information system accounts to [Assignment: organization-defined personnel or roles].

Atypical usage includes, for example, accessing information systems
at certain times of the day and from locations that are not consistent with the normal usage patterns of individuals working in organizations.

What would be helpful is if there was a way to indicate that we want the audit event when there is a policy violation but not to block the access. There may be a legitimate need to allow the login but the security officer just wants to be aware for possible follow up.

Version-Release number of selected component (if applicable):
pam-1.1.8-18.el7

Comment 4 Tomas Mraz 2017-05-22 08:55:20 UTC

Thinking about this more - this is actually already possible with the current pam_access and pam_time. You simply configure the PAM stack so the module is called but its return value is ignored.