McAfee EPOCDE-AA-BA Product Guide - Page 251

About reports, Structure of a report, Automation, Server Tasks, Actions, New Task, Run Query

Page 251 highlights

Querying the database and reporting on system status About reports 20 Task For option definitions, click ? in the interface. 1 Click Menu | Automation | Server Tasks , then click Actions | New Task. 2 On the Description page, type a name for the new task, then click Next. 3 From the Actions drop-down menu, select Run Query. 4 Click browse (...) next to the Query field and select a query. The Select a query from the list dialog box appears with the My Groups tab active. 5 Select the compliance-defining query. This could be a default query, such as McAfee Agent Compliance Summary in the Shared Groups section, or a user-created query, such as one described in Creating a query to define compliance. 6 From the Sub-Actions drop-down menu, select Generate Compliance Event and specify the percentage or number of target systems, then click Next. Events can be generated by the generate compliance event task if noncompliance rises above a set percentage or set number of systems. 7 Schedule the task for the time interval needed for Compliance History reporting. For example, if compliance must be collected on a weekly basis, schedule the task to run weekly. Click Next. 8 Review the details, then click Save. About reports Reports combine queries and other elements into PDF documents, providing detailed information for analysis. You run reports to find out the state of your environment - vulnerabilities, usage, events, etc. - so you can make the changes necessary to keep your environment secure. Queries provide similar information, but can only be used when you are directly interacting with an ePolicy Orchestrator server. Reports allow you to package together one or more queries into a single PDF document, enabling focused, offline analysis. Reports are configurable documents that display data from one or more queries, drawing data from one or more databases. The most recently run result for every report is stored within the system and is readily available for viewing. You can restrict access to reports through the use of groups and permission sets in exactly the same manner you restrict access to queries. Reports and queries can use the same groups, and because reports primarily consist of queries, this allows for consistent access control. Structure of a report Reports contain a number of elements held within a basic format. While reports are highly customizable, they have a basic structure that contains all of the varying elements. McAfee® ePolicy Orchestrator® 4.6.0 Software Product Guide 251

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328

Task
For option definitions, click
?
in the interface.
1
Click
Menu
|
Automation
|
Server Tasks
, then click
Actions
|
New Task
.
2
On the Description page, type a name for the new task, then click
Next
.
3
From the
Actions
drop-down menu, select
Run Query
.
4
Click browse (
...
) next to the Query field and select a query. The
Select a query from the list
dialog box
appears with the My Groups tab active.
5
Select the compliance-defining query. This could be a default query, such as
McAfee Agent Compliance
Summary
in the Shared Groups section, or a user-created query, such as one described in
Creating a
query to define compliance
.
6
From the
Sub-Actions
drop-down menu, select
Generate Compliance Event
and specify the percentage or
number of target systems, then click
Next
.
Events can be generated by the
generate compliance event
task if
noncompliance rises above a set percentage or set number of systems.
7
Schedule the task for the time interval needed for Compliance History reporting. For example, if
compliance must be collected on a weekly basis, schedule the task to run weekly. Click
Next
.
8
Review the details, then click
Save
.
About reports
Reports combine queries and other elements into PDF documents, providing detailed information for
analysis.
You run reports to find out the state of your environment — vulnerabilities, usage, events, etc. — so
you can make the changes necessary to keep your environment secure.
Queries provide similar information, but can only be used when you are directly interacting with an
ePolicy Orchestrator server. Reports allow you to package together one or more queries into a single
PDF document, enabling focused, offline analysis.
Reports are configurable documents that display data from one or more queries, drawing data from
one or more databases. The most recently run result for every report is stored within the system and
is readily available for viewing.
You can restrict access to reports through the use of groups and permission sets in exactly the same
manner you restrict access to queries. Reports and queries can use the same groups, and because
reports primarily consist of queries, this allows for consistent access control.
Structure of a report
Reports contain a number of elements held within a basic format.
While reports are highly customizable, they have a basic structure that contains all of the varying
elements.
Querying the database and reporting on system status
About reports
20
McAfee
®
ePolicy Orchestrator
®
4.6.0 Software Product Guide
251