# Separate a local cloud-app score override from a catalog correction request

> Should a disputed Defender for Cloud Apps score be overridden locally or submitted for catalog review?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-563-separate-a-local-cloud-app-score-override-from-a-catalog-correction-request/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:33+00:00
- Modified: 2026-09-10T02:14:31+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 2 minutes

## What you need to know

Should a disputed Defender for Cloud Apps score be overridden locally or submitted for catalog review?

## Potentially affected

Administrators reviewing application scores in the Defender for Cloud Apps catalog.

## DSE recommendation

Record whether the disagreement concerns organizational preference or inaccurate catalog evidence before choosing the change path.

## Article

## Source facts

Defender for Cloud Apps permits overriding one application’s score without changing the scoring weights. Microsoft recommends an app note explaining the override to other administrators. A separate review request can propose a new risk factor, revised score or correction to outdated app information. Score-metric settings instead change the importance of fields or categories; including N/A values contributes negatively to the calculation. An unscored app usually has unknown properties. [Microsoft Learn](https://learn.microsoft.com/en-us/defender-cloud-apps/risk-score).

## Applicability

Identify the precise catalog application and the disputed value. Keep a local acceptance decision separate from a claim that the vendor’s recorded attributes are wrong. This article addresses score administration, not a legal-compliance determination or proof that an application is safe.

## DSE recommendation

Record whether the disagreement concerns organizational preference or inaccurate catalog evidence before choosing the change path. For a local override, preserve the original value, reason, approver and review trigger in the app note and decision record. For an evidence correction, submit the disputed field and supporting material for catalog review. Avoid changing global weights merely to make one approved application reach a desired number. Treat unknown attributes as unanswered questions rather than silently converting them into assurance.

## Verification

After an authorized change, inspect the specific app’s displayed score and explanation. Check that broader scoring settings were not unintentionally altered. Track a catalog-review request separately until its outcome is known, and reconsider any temporary local override when the underlying information changes. In reporting, identify the score’s origin so readers can distinguish a locally chosen value from the catalog’s assessment.

## Official references

[Microsoft Learn: Find your cloud app and calculate risk scores](https://learn.microsoft.com/en-us/defender-cloud-apps/risk-score). Source reviewed September 9, 2026.

## Primary reference

- Name: Cloud app catalog and risk scores - Microsoft Defender for Cloud Apps | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/defender-cloud-apps/risk-score
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Separate a local cloud-app score override from a catalog correction request,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-563-separate-a-local-cloud-app-score-override-from-a-catalog-correction-request/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.