Bug 232995 - FIPS 200: limit the number of concurrent sessions
FIPS 200: limit the number of concurrent sessions
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
: FutureFeature
Depends On: 232993
  Show dependency treegraph
Reported: 2007-03-19 15:55 EDT by Chris Runge
Modified: 2008-04-04 07:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 07:53:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Runge 2007-03-19 15:55:03 EDT
+++ This bug was initially created as a clone of Bug #232993 +++

Requirement for FIPS 200

NIST 800-53
The information system limits the number of concurrent sessions for any user to
[Assignment: organization-defined number of sessions].


According to sgrubb:

"Just checked with pam maintainer and he feels that pam_limits covers this one. 
I think we should have the rejection tied to the audit system. So, we are 
closer than I thought. It should work so that we can check that item off, but 
we can make it better."
Comment 1 Tomas Mraz 2008-04-04 07:53:43 EDT
pam_limits is in RHEL-4 already the rejects based on concurrent sessions are
just not explicitely audited -> closing as NEXTRELEASE as RHEL-5 is fixed.

Note You need to log in before you can comment on or make changes to this bug.