APPS INTELLECT TRUST CENTER

Vulnerability management

How potential weaknesses are expected to be reported, assessed, prioritised and addressed.

Publication status: Draft / pending verification. This page describes Apps Intellect's proposed security governance and operating practices. It is not evidence that a control is implemented, tested or independently certified. Product- and environment-specific statements will be published only after technical verification and management approval.

Purpose

Vulnerability management is intended to identify weaknesses in applications, dependencies, container images, cloud configurations and supporting systems; assess their risk; and coordinate remediation and verification.

Intake and identification

Potential findings may arise from code and dependency scanning, cloud configuration reviews, security testing, vendor advisories, internal reports, customer reports or coordinated vulnerability disclosure. Each finding should be recorded with affected asset and version, source, discovery date, technical description, exposure, available exploit information and initial severity.

Risk-based prioritisation

Severity should consider technical severity and business context, including internet exposure, data sensitivity, exploitability, affected product versions, availability of mitigations and potential operational impact. A numerical scanner score should inform, but not replace, contextual assessment.

Remediation workflow

  1. Validate the finding and identify affected systems or releases.
  2. Assign an accountable owner and target remediation date based on risk.
  3. Apply a fix, configuration change, upgrade or documented mitigation.
  4. Test the change and confirm that the vulnerability is no longer present.
  5. Record closure evidence or obtain an authorised, time-bound risk exception.

Coordinated disclosure

External researchers and customers should report suspected vulnerabilities through the vulnerability disclosure page. Reports should include sufficient detail to reproduce the issue safely. Reporters should avoid accessing, modifying or deleting other people's data, disrupting services, or publicly disclosing a suspected issue before coordination.

Scanning and testing

Potential tools include dependency scanners, container scanners, static analysis and authorised dynamic testing. The use of a tool does not establish that all assets are covered or that a system is secure. Coverage, scan dates, exclusions, findings and remediation status should be retained as evidence.

Disclosure and customer communication

Confirmed issues that materially affect customers should be assessed for notification obligations and communicated through an appropriate channel, taking account of contractual commitments and applicable law. Public disclosure should be coordinated to reduce risk to customers and users.

Current status

Public pages do not disclose unresolved vulnerabilities, sensitive scan outputs or internal attack paths. Apps Intellect's current scan coverage, service-level remediation targets and outstanding finding counts remain pending verification.