Examples of file category changes after upgrading to Security for Microsoft SharePoint 3.5
Technical Articles ID:
KB85244
Last Modified: 5/21/2020
Last Modified: 5/21/2020
Environment
McAfee Security for Microsoft SharePoint (MSMS) 3.5
Summary
After upgrading from MSMS 3.0 to MSMS 3.5, obsolete file category names are removed.
If the file category filtering contains a Primary or Secondary table in MSME 3.0, those tables are migrated after upgrading to MSMS 3.5.
Policy Upgrade in Standalone Installation (SI)
If the file category filtering contains a Primary or Secondary table in MSME 3.0, those tables are migrated after upgrading to MSMS 3.5.
Policy Upgrade in Standalone Installation (SI)
During a product upgrade to MSMS 3.5, the installer manages the product configuration upgrade of both obsolete subcategories and secondary subcategory groupings.
After an upgrade, an HTML report is generated describing what changes were made to the policy. The report is generated at the bin folder in the Product installation directory for Standalone upgrades.
After an upgrade, an HTML report is generated describing what changes were made to the policy. The report is generated at the bin folder in the Product installation directory for Standalone upgrades.
The following table details how policies are migrated and cleaned up, and how equivalent entries are logged in the report:
|
Sl No.
|
Formats configured in MSMS 3.0
|
Formats migrated/removed in MSMS 3.5
|
Actions taken
|
|
1.
|
Rule1:
Documents\PFS: Write
|
|
Rule1 will be deleted because it has an obsolete file format.
Report Entry:
Rule "<Rule Name>" is removed as it has an obsolete File Format(s).
|
|
2.
|
Rule1:
Documents\PFS: Write
Documents\Microsoft Word
|
Rule1:
Documents\Microsoft Word
|
The obsolete format is removed but Rule1 persists because it has a supported format as well.
Report Entry:
Format Documents\ PFS: Write Word is removed as it is obsolete.
|
|
3.
|
Rule1:
Adobe PDF (Adobe Illustrator)
|
Rule1:
Adobe Acrobat (PDF)
|
Only the secondary subcategory is selected in MSMS 3.0. Rule1 will be migrated by selecting a primary or secondary subcategory. All formats within the subcategory are covered.
Report Entry:
Replaced file format Adobe PDF (Adobe Illustrator) with Adobe PDF under the category Graphics/Presentation.
|
|
4.
|
Rule1:
Adobe Acrobat (PDF)
Adobe PDF (Image)
Adobe PDF (Adobe Illustrator)
|
Rule1:
Adobe Acrobat (PDF)
|
Rule1 migrated: Only Adobe Acrobat (PDF) is selected because it covers the other two formats as well.
Report Entry:
Replaced file format Adobe Image with Adobe PDF under the category Graphics/Presentation.
Replaced file format Adobe Illustrator with Adobe PDF under the category Graphics/Presentation.
|
|
5.
|
Rule1:
Adobe Acrobat (PDF)
Adobe PDF (Image)
Rule2:
Adobe PDF (Adobe Illustrator)
|
Rule1(Rule2):
Adobe Acrobat (PDF)
|
After the rule migration, Rule1 will become duplicate of Rule2, so Rule2 is deleted and Rule1 is renamed as Rule1(Rule2).
Report Entry:
For Rule1 - Status will be Migrated:
Replaced file format Adobe Image with Adobe PDF under the category Graphics/Presentation.
For Rule2 - Status will be Removed:
Replaced file format Adobe Illustrator with Adobe PDF under the category Graphics/Presentation.
Rule2 is removed as it is duplicative of Rule1.
|
|
6.
|
Rule1:
Adobe Acrobat (PDF)
Adobe PDF (Image)
Rule2:
Adobe PDF (Adobe Illustrator)
OnAccess Policy:
Rule 1: Log & Allow Through
Rule 2: Log & Allow Through
|
Rule1(Rule2):
Adobe Acrobat (PDF)
OnAccess Policy:
Rule1(Rule2): Log & Allow Through
|
Rule2 in shared resource is removed and the actions linked to Rule2 are also removed because Rule1 covers it.
Report Entry:
For Rule1 - Status will be Migrated:
Replaced file format Adobe Image with Adobe PDF under the category Graphics/Presentation.
Rule2 action linked to Rule1 action since the rule is duplicative.
For Rule2 - Status will be Removed:
Replaced file format Adobe Illustrator with Adobe PDF under the Graphics/Presentation category.
Rule2 is removed as it is duplicative of Rule1.
|
|
7.
|
Rule1:
Adobe Acrobat (PDF)
Adobe PDF (Image)
Rule2:
Adobe PDF (Adobe Illustrator)
OnAccess Policy:
Rule1: Log & Prevent upload\download
Rule2: Log & Allow Through
|
Rule1(Rule2):
Adobe Acrobat (PDF)
OnAccess Policy:
Rule1(Rule2): Log & Prevent upload\download
|
As in the example above, if there is a change in the actions for the File Filter rules, when it is migrated, the higher order action between the rules is retained.
In this example, Prevent upload\download is of higher order than Allow Through. Therefore, the action is changed to Prevent upload\download.
Report Entry:
Same as in the above example and an additional entry is made in Rule1 –
Higher order action is retained in On-Access - Master Policy.
|
