Update Front Matter across SCBs and specific language in the Defender SCB to match OCC approved language

[ahuynhMITRE]

🗣 Description

OCC originally disapproved the consolidated baseline update document and SCBs for the Iceberg / Jellyfish release due to concerns that the SCBs may imply that CISA is telling the audience to upgrade their licenses to higher tier. The updates found in this PR include SCB changes to the front matter to address this concern.

💭 Motivation and context

Change is required for the consolidated change document and the SCBs to be approved for the version 1.4.0 release.
Closes #1393

🧪 Testing

N/A

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• Related issues these changes resolve are linked preferably via closing keywords.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.
• All relevant functional tests passed.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.

• Feature branch has been rebased against changes from parent branch, as needed

  Use Rebase branch button below or use this reference to rebase from the command line.

• Resolved all merge conflicts on branch

• Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[ahuynhMITRE]

Note: The SCBs language changes are expected to be reviewed by the lead lawyer at OCC on November 4th then routed to EAD (front office) for final review. This SCB update cannot be merged into MAIN until all parties above approve the updates!

[schrolla]

The changes look good to me, but I did notice that the introductions include the non-basic ASCII apostrophe's and double quotes around "as is". This doesn't hurt anything right now, but has caused issues with our automation for actual policy sections in the past. So might want to "flatten" these back to their basic ASCII equivalents in a future update.

[ahuynhMITRE]

@mitchelbaker-cisa added in @adhilto's additional links and resources, updated the implementation steps for DEFENDER.6.3v1, and added his note on log retention in the license requirements sections for Defender and EXO. Please take a look at all of the above and make any changes. Once approved will add to the consolidated change document to get routed up to EAD.

[mitchelbaker-cisa]

• AAD front matter looks good, left one comment for policy group 7 to verify license requirements language
• Exo looks good
• Teams front matter looks good, left one comment for policy group 6 to verify license requirements language
• Defender front matter looks good, left a couple comments for policy group 1 and 4 to verify license requirements language

[mitchelbaker-cisa]

Looks good, thanks for addressing those comments Andrew!

[ahuynhMITRE]

current status: routed back to CB Comms to go through final approvals on 11/7

[ahuynhMITRE]

@nanda-katikaneni & @schrolla Just got word from Chad that the SCBs have been approved! good to merge and add to 1.4.0 release!