INCA Internet Safe Deployment Practices (SDP)

V1.0 (Effective Date: 2026-11-17)

1. Purpose and Scope

INCA Internet Co., Ltd. ("the Company") applies safe deployment practices to reduce the risk of disruption and interruption to customers’ operations during security product updates, while maintaining both security and system stability. This document describes the principles governing pre-release validation, staged rollout, deployment health assessment, and response to issues when they occur.

These practices apply to the Windows antimalware products designated by the Company as in scope, and related components that affect their operation. The scope includes security content such as detection patterns and rules, engines, agents, drivers, and policy or configuration changes that affect protection behavior or stability.

The Company operates in a manner aligned with the safe deployment requirements of the Microsoft Virus Initiative (MVI). Specific validation activities and deployment methods may vary according to the type and risk of a change, product version, supported environment, and customer operating model. Supported products, versions, and environments are defined in the applicable official product information.

2. Change Impact Assessment and Release Ownership

Before deployment, changes are assessed based on their effects on protection, compatibility, performance, and the potential scope of disruption. Changes affecting kernel drivers, boot processes, file or network processing, and detection, remediation, or quarantine behavior are reviewed as changes requiring heightened scrutiny.

Development personnel review the change and its technical impact, and quality assurance personnel review validation results. A designated release approver considers the identified risks, validation results, and recovery options when deciding whether to release and whether to proceed to the next stage. Security content updates are not excluded from validation solely because of their release frequency.

3. Pre-release Quality and Compatibility Validation

Updates undergo validation appropriate to their impact before deployment. Key validation areas include:

  • Correct operation of changed functionality and regression testing of existing functionality.
  • Installation, upgrade, and uninstallation, and the loading and operation of services and engines.
  • Compatibility with supported Windows versions, hardware configurations, and representative business environments.
  • Impact on boot behavior and system performance, including CPU, memory, disk, and network usage.
  • Handling of failure conditions and recovery procedures, including interrupted updates, communication failures, and damaged packages.
  • Compatibility with Windows monthly updates and new versions.

Changes that directly affect system operation, such as driver changes, receive particular attention to stability in supported environments and compatibility with relevant Windows security features. General release is not approved while unresolved issues may materially affect customers.

4. Security Content Validation and False Positive Prevention

Security content, including detection patterns and rules, is evaluated for both its effectiveness against emerging threats and its risk of false positives affecting legitimate files or business applications. Validation against malicious and clean samples is performed before release, with checks for unintended detection, blocking, quarantine, or disruption of legitimate operations.

Content updates are managed with regard to both timely threat response and stability. Where detection effectiveness is inadequate or a significant false positive is identified, appropriate actions include holding, correcting, or withdrawing the affected content.

5. Deployment Integrity and Change Records

Code signing and package verification procedures appropriate to each component are applied to verify the origin and integrity of updates. Updates that fail integrity verification are not applied. Signing mechanisms and deployment privileges are managed through authorized personnel and procedures.

Released updates are assigned identifiable versions or release identifiers, and records of changes, validation results, and information needed for deployment and recovery are maintained. This supports identification of affected releases, issue investigation, and communication of fixes.

6. Internal Validation and Staged Rollout

Updates that may affect customer environments pass through test environments and controlled internal use before being deployed, starting with a limited population, and deployment scope is expanded progressively after results are reviewed. The deployment flow is as follows:

  1. Pre-release and internal validation: Validate functionality and stability in test environments and appropriate internal usage environments.
  2. Limited rollout: Apply the update to a limited population to assess its effect in operational environments. Necessary prior coordination is undertaken when customer environments are involved.
  3. Progressive expansion: Review deployment results and customer support information before expanding to the next deployment group.
  4. General release: Broaden distribution of updates that have passed the stage reviews, and continue assessing deployment health afterward.

Deployment group sizes and observation periods are determined by change risk and product-specific deployment methods. Security content updates and software or driver updates are managed according to their respective risks and deployment characteristics, rather than a single fixed schedule or percentage. For air-gapped or customer-managed environments, supported deployment methods and the customer’s change management procedures are taken into account.

7. Deployment Health Assessment and Progression Criteria

Results at each deployment stage are assessed based on available operational information, validation results, customer reports, and technical support information. Depending on the product and operating environment, the following are reviewed:

  • Compatibility information provided by Microsoft.
  • Installation and update outcomes and failure types.
  • Abnormal termination or operational failure of services, engines, or drivers.
  • Protection status and anomalies in detection or remediation behavior.
  • System performance degradation and compatibility issues with business applications.
  • False positive reports and update-related customer inquiries.

Progression between stages depends on whether predefined validation and stability criteria have been met. Deployment expansion is stopped for further assessment if a serious disruption, false positive, or compatibility issue is identified or remains under investigation. The scope and methods of obtaining operational information may vary with connectivity, product settings, and supported capabilities.

8. Deployment Suspension, Recovery, and Prevention of Recurrence

When an update-related issue is identified, its scope and severity are assessed, and appropriate actions are selected, such as suspending or withdrawing the deployment, adjusting problematic rules, releasing a fix, or providing a workaround. Where recovery to a previous version is supported and safe, a rollback to a validated version is performed, or recovery procedures are provided to customers.

Recovery methods vary by update type and product capabilities. If automatic recovery is not supported, or reverting to a previous version is inappropriate, manual steps guided by technical support or application of a corrective update are used. Response decisions take account of both restoration of service and potential gaps in protection.

Resumption of deployment is decided after root cause analysis, corrective action, revalidation, and approval. Significant deployment incidents are reviewed, and findings are incorporated into improvements to testing, release criteria, and response procedures. The Company cooperates with Microsoft where necessary.

9. Emergency Updates

Emergency updates may be performed to address active threats, serious product failures, or urgent compatibility issues. Even in such cases, essential functional, stability, and integrity validation, approval, deployment health assessment, and review of recovery options are performed.

Observation periods or deployment stages may be adjusted by weighing threat response urgency against deployment risk, and the reasons for adjustment and the approval are recorded. Health assessment is intensified after an emergency release, and the response is reviewed afterward.

10. Customer Update Operations

Customers can manage updates for their operating environments using the update settings and official support procedures available for the applicable product. Available management controls and limitations vary by product, version, and deployment model.

For business-critical systems, prior testing and a limited pilot before wider deployment are recommended where supported. When considering update deferral or a version change, customers should consider both delayed protection against emerging threats and compatibility impacts. Technical support can be consulted on the appropriate deployment approach when needed.

11. Customer Communication and Diagnostic Information

When a deployment issue materially affects customers, necessary information is provided through security or support notices on the official website or through the product’s official customer support channels. Guidance includes, within the confirmed scope, affected products, versions, and environments; key symptoms; recommended actions; fixes; and recovery methods.

When logs or diagnostic information are requested for investigation, the purpose of collection and the necessary scope are explained, and the information is handled in accordance with the applicable product or service privacy notice and contractual procedures. Public communications do not include customer confidential information, unnecessary personal information, authentication credentials, or private signing information.

12. Review and Improvement

INCA Internet reviews these safe deployment practices at least once a year. They are also reviewed following significant deployment incidents, changes to product architecture, or changes to relevant platform or program requirements, and necessary improvements are incorporated. For material revisions, the revision date and change history on this page are updated.

13. Revision History

DateVersionDescription
1.0Initial Release