Which file characteristic cannot be used in the Cisco IronPort Data Security policies?

Question

Options

• Afilename
• Bfile age
• Cfile size
• Dfile type

• A
  6% (1)
• B
  88% (15)
• D
  6% (1)

Explanation

File age is not a supported criterion in Cisco IronPort Data Security policies because these policies are designed to inspect file content and attributes at the point of transfer - not metadata tied to when a file was created or last modified. The IronPort platform simply does not expose file age as a filterable property in its Data Loss Prevention (DLP) and data security rule engine.

Why the distractors are wrong:

• A (filename): Filename is supported - policies can match on specific filenames or wildcard patterns to block or monitor transfers.
• C (file size): File size is supported - you can set thresholds to flag or block uploads/downloads exceeding a defined size.
• D (file type): File type is supported - IronPort inspects MIME types and file extensions to enforce type-based restrictions.

Memory tip: Think of the three things you can see in the moment about a file - its name, size, and type. File age requires historical context (a timestamp from the filesystem), which IronPort Data Security policies don't have access to during inspection. If it's a "time-based" property, it's out.

No community discussion yet for this question.