A SaaS policy that says "each application must be configured to an approved baseline" achieves nothing until someone writes down, per application, which settings, at which values, checked how often and signed off by whom. This template is that standard. It sets the minimum controls every business SaaS application must meet at each risk tier, the per-application baseline record an owner completes and signs, and the drift checks that keep the tenant on the baseline. It sits under the SaaS Security Policy Template, which sets intent and tiering, and after the SaaS Application Security Review Checklist, which decides whether an application is bought at all. It is for SaaS platform owners, identity teams and security architects who run applications day to day.
How to use this template
- Replace text in square brackets, such as [Organisation], [CISO], [SaaS register] and [30 days], with your own values. Bracketed values are suggested defaults, not external requirements.
- "Must" is mandatory for the tier shown. "Should" is expected unless a deviation is recorded under section 8.
- Use the tier definitions from your SaaS security policy. This standard does not re-tier applications; it says what each tier must have.
- Sections 4 and 5 are the organisation-wide minimum. Section 6 is the per-application record: copy it once for each Tier 1 and Tier 2 application and fill it in with the application's own setting names.
- Where a published baseline exists for a product, such as CISA's SCuBA baselines for Microsoft 365 and Google Workspace or a CIS Benchmark, adopt it as the application record and note your deviations, rather than writing settings from scratch.
1. Purpose
This standard sets the minimum security configuration for SaaS applications used by [Organisation] and the process for recording, approving and checking each application's baseline, so that every application is configured to a known, approved state and departures from it are detected and corrected within set times. It implements section [4.4 Configuration baselines] of the [Organisation] SaaS Security Policy.
2. Scope
- All SaaS applications recorded in [the SaaS register] at Tier 1 (high), Tier 2 (medium) or Tier 3 (low).
- Tenant-level settings the customer controls: authentication, sessions, administration, sharing, integrations, data protection, logging and notification.
- Non-human identities created in or for each application: integration users, API tokens, service principals, app passwords and OAuth grants.
- Out of scope: provider-side controls (covered by vendor assurance at purchase), and application selection and approval (covered by the policy and review checklist).
3. Roles and responsibilities
| Role | Responsibility under this standard |
|---|---|
| [CISO] or delegate | Owns this standard; approves Tier 1 baseline records and deviations rated high |
| Application owner | Completes and signs the baseline record (section 6); remediates drift; renews deviations |
| Platform administrator | Applies settings; documents setting names and values; runs or reviews drift checks |
| [Security team] | Reviews records, operates automated assessment (SSPM or baseline tools), reports conformance |
| [Identity team] | Owns SSO, MFA, conditional access and privileged role settings across applications |
4. Minimum controls by tier
Each application must meet every control marked for its tier. "Where supported" means the control applies if the product offers it in the plan [Organisation] holds; if it does not, record the gap and compensating control in section 6.
| ID | Control | Tier 1 | Tier 2 | Tier 3 |
|---|---|---|---|---|
| BL-01 | Sign-in through [corporate identity provider] by SSO; local passwords disabled for users except named break-glass accounts | Must | Must, where supported | Should |
| BL-02 | MFA enforced for all users; phishing-resistant MFA for administrators | Must | Must (phishing-resistant for admins: Should) | Must (via SSO or app MFA) |
| BL-03 | Legacy and basic authentication protocols and app passwords disabled | Must | Must, where supported | Should |
| BL-04 | Session lifetime and re-authentication set to [12 hours] or less for users, shorter for admins | Must | Should | Should |
| BL-05 | Automated provisioning and deprovisioning (SCIM or identity provider connector) | Must, where supported | Should | Not required |
| BL-06 | Between [2] and [4] standing top-level administrators, named, with separate admin accounts; other admins in least-privilege roles | Must | Must | Should |
| BL-07 | Just-in-time or approval-based elevation for the highest admin role | Must, where supported | Should | Not required |
| BL-08 | External sharing limited to approved domains or existing guests; default sharing scope "specific people" | Must | Should | Should |
| BL-09 | Public or "anyone" links disabled or expiring in [30 days] or less, view-only by default | Must | Must | Should |
| BL-10 | Guest access reviewed every [90 days]; guests cannot invite other guests | Must | Should | Not required |
| BL-11 | User consent to third-party apps restricted; admin consent workflow for apps requesting high-risk scopes | Must | Must | Should |
| BL-12 | Every integration user, API token and OAuth grant recorded with an owner and expiry; no non-expiring tokens without a deviation | Must | Must | Should |
| BL-13 | Automatic forwarding of mail or records to external destinations disabled | Must, where relevant | Must, where relevant | Should |
| BL-14 | Audit logging enabled for admin, sign-in, sharing and data access events, retained [12 months] (searchable [3 months]) and forwarded to [SIEM] | Must | Must (forwarding: Should) | Should |
| BL-15 | Alerts for admin role changes, new high-scope app consents and mass download or export | Must | Should | Not required |
| BL-16 | Data loss prevention or sensitivity labelling applied to [Confidential] data | Should, where supported | Should, where supported | Not required |
| BL-17 | Security contact and admin notification addresses set to a monitored [shared mailbox] | Must | Must | Must |
| BL-18 | Tenant configuration exported or backed up after each approved change | Should | Should | Not required |
The defaults above follow published baselines where they exist. For example, the SCuBA Microsoft 365 baselines require legacy authentication to be blocked (MS.AAD.1.1v1), user consent to applications to be restricted (MS.AAD.5.2v1), automatic forwarding to external domains to be disabled (MS.EXO.1.1v2) and "Anyone" links to expire in 30 days or less (MS.SHAREPOINT.3.1v1). The Google Workspace baselines require a 12-hour re-authentication (GWS.COMMONCONTROLS.4.1v1), external Drive sharing restricted to allowlisted domains (GWS.DRIVEDOCS.1.1v1) and audit logs searchable for at least 3 months and retrievable for at least 12 months (GWS.COMMONCONTROLS.14.2v1). See the CISA SCuBA Baselines Guide.
5. Selecting the reference baseline
- Where CISA SCuBA publishes a baseline for the product, Tier 1 records must use it as the reference and record each policy ID that is not met.
- Where a CIS Benchmark exists, it should be used as the reference or a secondary check. See the CIS Benchmarks Guide.
- Where neither exists, the record must map the controls in section 4 to the product's own setting names, using the provider's security or administration documentation, and may draw on the Cloud Security Alliance SaaS Security Capability Framework (SSCF) for the list of customer-configurable capabilities to look for.
- The reference and its version must be named in the record, so later changes to the reference can be assessed.
6. Per-application baseline record
Complete one record per Tier 1 and Tier 2 application. Keep it in [the configuration repository] under version control.
| Field | Content |
|---|---|
| Application and tenant | [Name], tenant ID or URL, plan or licence edition |
| Tier and data classification | From [the SaaS register] |
| Reference baseline | [SCuBA / CIS Benchmark / own mapping], version and date |
| Setting table | For each section 4 control and each reference policy: setting path, required value, current value, status (met, deviation, not available in plan) |
| Non-human identities | Each integration user, token, service principal and OAuth app with owner, scopes and expiry |
| Deviations | Deviation ID, control, reason, compensating control, risk rating, approver, expiry |
| Drift check method | Tool or manual procedure, frequency, who reviews the output |
| Sign-off | Application owner name and date; [CISO] approval for Tier 1; next review date |
The application owner must sign the record before go-live and at each review. A record with an expired sign-off counts as non-conformant.
7. Drift checks
- Tier 1 applications must be assessed against their record at least [monthly], automatically where tools allow (for example ScubaGear for Microsoft 365, ScubaGoggles for Google Workspace, or an SSPM platform). See the Configuration Drift and Baseline Enforcement Guide.
- Tier 2 applications must be assessed at least [quarterly]; Tier 3 at renewal.
- Drift must be remediated within [7 days] for BL-01 to BL-03, BL-06, BL-11 and BL-14, and within [30 days] for other controls, or a deviation raised.
- Provider release notes and new feature announcements for Tier 1 applications must be reviewed [monthly] for new settings with permissive defaults; new settings are added to the record within [30 days].
- Assessment output must be retained for [12 months] as audit evidence.
8. Deviations
- A setting that cannot meet the standard must be recorded as a deviation with a compensating control, risk rating and expiry of no more than [12 months].
- Deviations rated high must be approved by [CISO]; others by [the security team].
- "Not available in our plan" is a deviation, not an exemption. It must state whether a licence upgrade was considered.
- Expired deviations count as drift. Use the Hardening Exceptions and Compensating Controls Template for the register.
9. Change control
- Changes to Tier 1 settings covered by the record must go through [change management], with the record updated in the same change.
- Emergency changes must be recorded within [2 working days] and reviewed at the next drift check.
- This standard is versioned separately from the policy and may be updated by [CISO] without re-approving the policy.
10. Compliance, review and approval
- [Security team] reports conformance per tier to [the risk committee] [quarterly].
- This standard is reviewed at least [annually] and when a reference baseline issues a new major version.
- Approved by: [Name, role], [date]. Version: [1.0]. Next review: [date].
Implementation guidance
Rollout
- Start with identity and collaboration. Write records first for the identity provider and the main collaboration suite, where published baselines and free assessment tools already exist.
- Assess before enforcing. Run the baseline tool in report mode, record current values, and agree deviations before changing anything.
- Pilot changes. Apply restrictive settings (sharing, consent, legacy protocols) to a pilot group or organisational unit first, then widen. Keep the prior configuration export so a change can be rolled back.
- Extend to other Tier 1 applications. Map section 4 to each product's setting names using provider documentation; the Microsoft 365 Security Checklist and Google Workspace Security Checklist show the level of detail expected.
- Automate drift checks. Move from manual review to scheduled tool runs feeding [SIEM] or a ticket queue.
Measuring it
- Share of Tier 1 and Tier 2 applications with a current signed record.
- Baseline conformance per application (controls met as a share of applicable controls).
- Median time to remediate drift, against the section 7 targets.
- Open deviations and expired deviations per tier.
- Integration tokens or OAuth grants without an owner or expiry.
Framework mapping
| Framework | Reference | Sections |
|---|---|---|
| NIST SP 800-53 Rev 5 | CM-2 Baseline Configuration; CM-6 Configuration Settings; CM-3 Configuration Change Control | 4, 6, 9 |
| NIST SP 800-53 Rev 5 | CA-7 Continuous Monitoring | 7 |
| NIST CSF 2.0 | PR.PS-01 Configuration management practices are established and applied | 4 to 9 |
| CIS Controls v8.1 | Control 4 Secure Configuration of Enterprise Assets and Software | 4 to 7; see the CIS Control 4 guide |
| ISO/IEC 27001:2022 Annex A | 8.9 Configuration management; 5.23 Information security for use of cloud services | 4 to 9 |
Sources for the default values
- CISA: Secure Cloud Business Applications (SCuBA) Project
- CISA: ScubaGear and Microsoft 365 baselines
- CISA: ScubaGoggles and Google Workspace baselines
- CIS: Microsoft 365 Benchmark
- Cloud Security Alliance: SaaS Security Capability Framework (SSCF)
Related NHI Mgmt Group resources: SaaS Security Policy Template · SaaS Application Security Review Checklist · SaaS Security Guide · SaaS and OAuth App Governance Guide