Home » McAfee Manuals » Computer Software » McAfee PASCDE-AB-IA » Manual Viewer

McAfee PASCDE-AB-IA Product Guide - Page 61

File versioning, Wildcard characters, File validation

View all McAfee PASCDE-AB-IA manuals

Add to My Manuals
Save this manual to your list of manuals

Page 61 highlights

File Integrity Monitoring and entitlement reporting How file integrity monitoring works Wildcard characters Monitored and excluded paths and file names support the * and ? wildcard characters. The * wildcard character represents one or more characters and the ? wildcard represents a single character. You can choose to monitor a single file by typing the name of the file when you create a file integrity monitoring policy. By using wildcard characters, you can monitor files or paths of a specific type. For example, if you type ?:\Config for the path and *.txt for the file, McAfee Policy Auditor monitors all text files in the Config folder on all hard drives. You can exclude specific paths and files in a similar manner. File validation McAfee Policy Auditor does not validate the existence of files. It ignores paths or files that do not exist. File versioning McAfee Policy Auditor allows you to store up to six versions, including the file baseline, of text files from managed systems. The software does not support versioning for non-text files. NOTE: The actual text files are not stored in the software database. The database stores the text file contents for quick comparison purposes, even when the system is not connected to the network. When you create a policy, you have the opportunity to store file versions for comparison purposes. The number of file versions you can store ranges from 2 to 6. This number includes the baseline version. File versions are stored on a First In, First Out (FIFO) basis. For example, if you configure the software to store 3 versions, it stores the baseline version plus the two most recent versions. If the file changes, the oldest non-baseline file is purged to recover disk space by an internal server task that runs once a day by default. Configuring the maximum number of stored file versions When you create a file integrity monitoring policy, you can specify the maximum file size stored for each version with the Max versioned file size setting. The available settings range from 1 to 4 MB. For example, if you set Max versioned file size to 3 MB, the text in the file is stored when its size is less than or equal to 3 MB. If the file size exceeds 3 MB, the software alerts you with an error message. If you receive an error message, you can edit the policy so that it stores text from files as large as 4 MB. Configuring the maximum number of file integrity monitoring files You can configure how many versions of files are stored by the software. Use the Server Settings page to set the number of file versions stored by McAfee Policy Auditor. For more information, see Max number of FIM version files and Edit Server Settings in the Getting Started with McAfee Policy Auditor Software section. McAfee Policy Auditor 6.0 software Product Guide for ePolicy Orchestrator 4.6 61

Section	Page
Contents	3
Introducing McAfee Policy Auditor	8
Audience	8
Conventions	8
Finding product documentation	9
Getting started with McAfee Policy Auditor	10
Introduction to compliance audits	10
Auditing systems	11
What's new	11
Software components and what they do	12
Use of ePolicy Orchestrator software features	13
Managed systems vs. unmanaged systems	14
Configuring McAfee Policy Auditor	16
Server settings and what they control	16
Edit McAfee Policy Auditor server settings	18
How permission sets work	18
Default permission sets	19
Edit permission sets	21
Using the McAfee Policy Auditor agent plug-in	22
The agent plug-in and how it works	22
Supported platforms	22
How content is managed	24
Install and uninstall the agent plug-in	24
Install the McAfee Policy Auditor agent plug-in	24
Uninstall the agent plug-in	25
Send a manual wake-up call to a group of systems	25
Display the system tray icon on Windows systems	26
Configuring agentless audits	27
How McAfee Policy Auditor integrates with the McAfee Vulnerability Manager extension	27
Uniform system management	27
McAfee Vulnerability Manager extension integration with scannable systems	28
Asset Discovery scans	28
Data collection scans	28
The Maintain Foundstone Audits server task	28
The Data Import server task	29
Server support	29
Configure McAfee Vulnerability Manager and the ePolicy Orchestrator extension	29
Create a McAfee Vulnerability Manager workgroup	30
Configure the McAfee Vulnerability Manager single sign-on feature	30
Create a data source to synchronize McAfee Vulnerability Manager and ePolicy Orchestrator	31
Register a McAfee Vulnerability Manager database server with McAfee Policy Auditor	32
Manage McAfee Vulnerability Manager credential sets	33
Create an Asset Discovery scan	33
Create an MVM Data Import task	34
Add systems found by McAfee Vulnerability Manager scans to the System Tree	35
Create a Data Collection Scan	35
View McAfee Vulnerability Manager scan status	36
How to handle missing audit results	36
Troubleshoot missing audit results	37
How to handle mismatched McAfee Vulnerability Manager certificates	37
Troubleshoot mismatched McAfee Vulnerability Manager certificates	38
Creating and managing audits	39
Audits and how they work	39
Audit frequency	40
When audits are run	40
Per audit data maintenance	40
Benchmark profiles and their effect on audits	41
Considerations for including systems in an audit	41
Benchmark labels and how they are used	41
Findings	42
Agentless audits	42
Activate benchmarks	42
Create an audit	43
Run an audit manually	43
Disable an audit	44
Delete audits	44
Audit whiteout and blackout periods	44
Set whiteout and blackout periods	44
Service Level Agreements	45
Create, edit, and delete Service Level Agreements	45
How viewing audit results works	46
Exporting audits and audit results	47
Export audits	47
Scoring Audits	49
Default scoring model	49
Flat unweighted scoring model	50
Flat scoring model	50
Absolute scoring model	51
Changing the scoring model	51
Managing Audit Waivers	52
Types of waivers	52
Exception waivers	53
Exemption waivers	53
Suppression waivers	53
Waiver status	54
Filtering waivers by status	54
How start and expiration dates work	54
Examples of filtering waivers by date	54
Filtering waivers by date	55
Filtering waivers by group	55
How waiver requests and grants work	56
Requesting waivers	56
Granting waivers	57
Making waivers expire	57
Deleting waivers	57
File Integrity Monitoring and entitlement reporting	59
How file integrity monitoring works	59
File information monitored	60
File baselines	60
Monitored and excluded files	60
File versioning	61
File version comparison	62
Accept file integrity monitoring events	62
Purge file integrity monitoring events	62
Entitlement reporting	62
Create and apply a file integrity monitoring policy	63
Create a file integrity monitoring policy	63
Apply a policy to systems	65
Compare file versions	65
Accept file integrity monitoring events	66
Purge file integrity monitoring events	66
Create a new file integrity monitoring baseline	67
Query reports for file integrity monitoring	67
Rollup reporting	68
Rollup capabilities	68
Rollup reporting considerations	68
Rollup server tasks	69
Rollup Data - PA: Audit Benchmark Results	69
Rollup Data - PA: Audit Rule Result	70
Rollup Data - PA: Audit Patch Check Result	71
Rollup reports	71
Configure rollup reporting	72
Findings	74
How findings work	74
Types of violations	74
Violation limit	75
Other Findings enhancements	75
Hide or unhide Findings results	75
Dashboards and Queries	77
Policy Auditor default dashboards	77
PA: Compliance Summary dashboard	80
PA: MS Patch Status Summary dashboard	80
PA: Operations	80
PA: PCI Summary	81
Queries as dashboard monitors	82
Policy Auditor agent plug-in debug tool	83
Execute the agent plug-in debug tool	83
Display help	84
Run an audit	84
Run a benchmark	85
Run a check	85
Save debug information	86
Appendix A: Implementing the Security Content Automation Protocol	87
Statement of FDCC compliance	87
Statement of SCAP implementation	88
Statement of CVE implementation	88
Statement of CCE implementation	89
Statement of CPE implementation	89
Statement of CVSS implementation	90
Statement of XCCDF implementation	90
Statement of OVAL implementation	90
Appendix B: Common Criteria requirements	92

Match case Limit results 1 per page

Wildcard characters

Monitored and excluded paths and file names support the

and

wildcard characters. The

wildcard character represents one or more characters and the

wildcard represents a single

character.

You can choose to monitor a single file by typing the name of the file when you create a file

integrity monitoring policy. By using wildcard characters, you can monitor files or paths of a

specific type. For example, if you type

?:\Config

for the path and

*.txt

for the file, McAfee Policy

Auditor monitors all text files in the

Config

folder on all hard drives.You can exclude specific

paths and files in a similar manner.

File validation

McAfee Policy Auditor does not validate the existence of files. It ignores paths or files that do

not exist.

File versioning

McAfee Policy Auditor allows you to store up to six versions, including the file baseline, of text

files from managed systems.The software does not support versioning for non-text files.

NOTE:

The actual text files are not stored in the software database.The database stores the

text file contents for quick comparison purposes, even when the system is not connected to the

network.

When you create a policy, you have the opportunity to store file versions for comparison purposes.

The number of file versions you can store ranges from 2 to 6.This number includes the baseline

version.

File versions are stored on a First In, First Out (FIFO) basis. For example, if you configure the

software to store 3 versions, it stores the baseline version plus the two most recent versions.

If the file changes, the oldest non-baseline file is purged to recover disk space by an internal

server task that runs once a day by default.

Configuring the maximum number of stored file versions

When you create a file integrity monitoring policy, you can specify the maximum file size stored

for each version with the

Max versioned file size

setting.The available settings range from 1

to 4 MB.

For example, if you set

Max versioned file size

to 3 MB, the text in the file is stored when its

size is less than or equal to 3 MB. If the file size exceeds 3 MB, the software alerts you with an

error message. If you receive an error message, you can edit the policy so that it stores text

from files as large as 4 MB.

Configuring the maximum number of file integrity monitoring files

You can configure how many versions of files are stored by the software. Use the Server Settings

page to set the number of file versions stored by McAfee Policy Auditor. For more information,

see

Max number of FIM version files

and

Edit Server Settings

in the

Getting Started with McAfee

Policy Auditor Software

section.

File Integrity Monitoring and entitlement reporting

How file integrity monitoring works

McAfee Policy Auditor 6.0 software Product Guide for ePolicy Orchestrator 4.6