Configuration Update Frequency

Plan	Platforms	MASVS
Enterprise	Android, iOS	Not mapped

Overview

Configuration Update Frequency controls whether a protected app checks AppTego for updated security policy after release. It allows teams to adjust controls, messages, pins, and response behavior without waiting for a full app-store release.

Unlike Enforce Latest Configuration, this control is designed for graceful background refresh. If an update cannot be fetched, the app continues with the most recent valid policy it already has.

When To Use It

Enable configuration updates when:

You need to adjust control settings after release.
You want faster rollout of certificate, attestation, fraud, or response changes.
Your users usually have network connectivity.
You want policy flexibility without forcing every change through a new binary release.

Disable configuration updates when:

The app must operate fully offline.
Network egress is tightly restricted.
A fixed build-time policy is required for compliance or operational reasons.
You prefer all policy changes to move through your standard app release process.

How It Works

When updates are enabled, the protected app periodically checks AppTego for the latest valid policy, verifies it, stores it locally, and uses it for subsequent protection decisions. If no update is available, or if the device cannot reach the service, the app keeps using the last valid local policy.

Public documentation does not expose tenant secrets, policy URLs, signing-key material, or internal request formats. Those values are generated and handled by AppTego.

How to Enable the Control

Navigate to Device Settings from the AppTego portal, and expand the App Lifecycle section. Under this section you will find the Check For Configuration Updates control. Click Enable to enable it for the next build or for it to be applied with a live push (if enabled).

API Configuration Example

{
  "ConfigurationUpdateFrequency": {
    "protection": true
  }
}

Field	Purpose
`protection`	Enables check for configuration updates for protected apps.

Operating Modes

Mode	Behavior
Updates enabled	The app can receive policy changes after release and falls back gracefully if offline.
Updates disabled	The app uses only the policy packaged into the protected build.
Updates plus enforce mode	The app must verify current policy before protected controls proceed.

Compatibility Notes

Background updates improve response time to new threats, but they still depend on device connectivity.
Disabling updates can simplify offline operation, but policy changes require a rebuilt app.
Apps with strict availability requirements should test poor-network behavior before enabling enforce mode.
Apps with strict security requirements should consider pairing this with Enforce Latest Configuration.