Sponsored Content
Operating Systems Linux Red Hat Looking for PCI Compliance tool for Redhat Lix. Post 302830403 by sahasuman on Monday 8th of July 2013 04:24:05 PM
Old 07-08-2013
Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this: 1. Options outside any brackets are mandatory 2. Options inside these < .. > are mandatory too 3. Options inside ... (4 Replies)
Discussion started by: vkleban
4 Replies

3. Red Hat

Patch analysis tool Redhat Enterprise release 4

Hello I have been asked to provide a security patch analysis of servers in my environment. For HPUX and Solaris there are tools wich can be loaded onto the servers to do this. However I do not know of one for Redhat . At this point I must mentioned that the Redhat servers are behind a firewall... (2 Replies)
Discussion started by: dmsmith32
2 Replies

4. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port... (2 Replies)
Discussion started by: saurabh84g
2 Replies

5. Shell Programming and Scripting

Inotifywait tool in no there in Redhat 5.6

Hi, I want to monitor any new file to be created in some of the directory using inotifywait tool but this is not available in Redhat 5.6. Could you please let me know how to achieve (monitoring of file) without using inotifywait too? Because i dnt want to install this tool due to some reason.... (1 Reply)
Discussion started by: Pawan Kumar
1 Replies

6. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies

7. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from... (11 Replies)
Discussion started by: wisecracker
11 Replies
pluginkit(8)						    BSD System Manager's Manual 					      pluginkit(8)

NAME
pluginkit -- plugin plug-in extension pluginkit SYNOPSIS
pluginkit -m [-ADv] [-p -protocol] [-i -identifier] [key=value] [...] pluginkit [-ar] [-v] [file ...] pluginkit -e election [-p -protocol] [-i -identifier] [key=value] [...] DESCRIPTION
pluginkit manages the PlugInKit subsystem for the current user. It can query the plug-in database and make limited interventions for debug- ging and development. A list of flags and their descriptions: -A, --all-versions Matches find all versions of a given plug-in known to the system. By default, only the latest (highest) version is returned. -a Explicitly adds plugins at the file location(s) given, even if they are not normally eligible for automatic discovery. Note that database clean-ups may eventually remove them in that case. -e election Perform a matching operation (see -m) and apply the given user election setting to all matching plug-ins. Elections can be "use", "ignore", and "default". Elections are applied to all plug-ins with given identifier. -D, --duplicates Matches find all physical instances of a given plug-in known to the system, even multiple copies with the same version. -i, --identifier identifier Specifies a plug-in identifier to match, a short-hand for NSExtensionIdentifier=identifier. -m --match Requests pluginkit to scan all registered plug-ins for those matching the given search criteria (see DISCOVERY MATCHING below). All matching plug-ins are returned, one per line. Add the -v option to get more detailed output. This is exactly reproducing the func- tionality of PlugInKit discovery, except that no host-specific restrictions are imposed. The -A and -D options affect the outcome. -p --protocol protocol Specifies a plug-in protocol to match, a short-hand for NSExtensionPointName=protocol. -r Explicitly removes plugins at the file location(s) given. Note that automatic discovery procedures may add them back if they are still present. --raw Present replies from the management daemon (pkd) in raw XML form. This is primarily useful for debugging and for reporting full state in bug reports. -v Asks for more verbose operation. For matching requests, more detail is printed about each matched plug-in. This option can be given more than once. DISCOVERY MATCHING
During plug-in discovery, PlugInKit matches plug-ins against match criteria and delivers matching plug-ins. Only plug-ins that match all given criteria are eligible. Criteria are expressed as "key" (must be present) or "key=value" (key must be present and have the given value). The -i and -p arguments are shorthands for the conventional identifier and protocol matching keys. All matching plug-ins are reduced accord- ing to the -A and -D options given. With -D, all eligible plug-ins are returned. With -A, the last-registered (by timestamp) instance of each version is returned. By default, only the last instance of the highest version is returned. Note that this reduction is applied after match- ing. EXPLICIT CHANGES
The -a and -r options make changes to the system's plug-in registry. The registry is designed to operate automatically, and will update on its own as applications are installed, removed, and discovered. The options available through pluginkit are intended only for limited manipu- lation during plug-in development and for certain maintenance tasks. They cannot make permanent alterations of the automatic registry state. SEE ALSO
pkd(8), launchd(8) HISTORY
The pluginkit command first appeared in OS X 10.9. Darwin May 31, 2019 Darwin
All times are GMT -4. The time now is 07:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy