Government Security Standard Compliant Kickstarts 0.01 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Government Security Standard Compliant Kickstarts 0.01 (Default branch)
# 1  
Old 04-19-2008
Government Security Standard Compliant Kickstarts 0.01 (Default branch)

Are you responsible for compliance with variousgovernment security standards? Are you tired ofdesigning and maintaining these baselinesyourself? The goal of this project is to createstandards compliant kickstart files for standardssuch as DCID, STIG, NIST, and others.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. HP-UX

Security hardening for standard HP-UX users

Hi, The standard accounts that are created during the HP-UX installation, eg, bin,adm,daemon,uucp,lp,hpdb and nobody have their own shell. Will there be any impact if we change these user's shell to /bin/false? Like processes get interrupted, files cannot be generated, etc. Regards (3 Replies)
Discussion started by: anaigini45
3 Replies

2. News, Links, Events and Announcements

Red Hat Linux gets top government security rating

By Robert McMillan, IDG News Service, 06/15/07 Red Hat Linux gets top government security rating (0 Replies)
Discussion started by: Neo
0 Replies

3. Shell Programming and Scripting

Security Issue with Standard Input?

Hi Gang, Running a script in AIX 5.3. Users wanted me to add a "confirm you want to run script, enter 'y' or 'n'" kind of thing... here is what I came up with: #!/bin/sh myfile=`basename "$1"` dateNow=`date "+%m.%d.%Y.%H.%M.%S"` # Get current date mydatedfile=$myfile.$dateNow... (2 Replies)
Discussion started by: yall
2 Replies
Login or Register to Ask a Question
secdef(3)						     Library Functions Manual							 secdef(3)

NAME
secdef: open_secdef(), close_secdef(), get_secdef_str(), get_secdef_int() - security defaults configuration file routines SYNOPSIS
DESCRIPTION
opens the security configuration file This function must be called prior to calling or closes the security configuration file. and return the value of the specified parameter defined in the security configuration file. See the security(4) manpage. Programs using these routines must be compiled with APPLICATION USAGE
In a multithreaded application, these interfaces are thread-safe, but not async-cancel-safe. A cancellation point may occur when a thread is executing any of these interfaces. RETURN VALUE
returns a value of if the open completed successfully. Otherwise, it returns and leaves unchanged from the call. and return the follow- ing: The value of the specified parameter was successfully returned. The entry was not found, or the security configuration file was not opened. The format of the entry was incorrect. EXAMPLES
This example obtains the "path" from the parameter. FILES
Security defaults configuration file. SEE ALSO
security(4). secdef(3)