Policy Reference

Policy tiers

Policies are organized into tiers: Balanced, Strict, and Hardened. Each tier adjusts control-flow complexity, string encryption density, and anti-tamper coverage.

• Balanced: recommended default for most modules
• Strict: higher protection for sensitive paths
• Hardened: highest protection for critical flows

Scopes and overrides

Use scopes to target specific packages, modules, or binaries. Overrides allow fine-grained control over specific classes or symbols.

scopes:
  - name: licensing
    match: com.obfguard.licensing.*
    tier: hardened
  - name: ui
    match: com.obfguard.ui.*
    tier: balanced

Exclusions

Exclude third-party SDKs or reflection-heavy modules if needed. Exclusions are explicit and auditable.

• Exclude packages with dynamic loading
• Skip generated code or protobuf modules
• Keep analytics SDKs unmodified

Reporting settings

Reporting controls determine how much detail is captured in the protection report. Use detailed reporting for audits and standard reporting for daily releases.

• Coverage summary by module
• List of protected symbols
• Integrity checks enabled
• Policy version used

Best practices

• Start with Balanced, then elevate sensitive scopes
• Document all overrides with a short rationale
• Review protection reports after each release
• Keep policy files under version control