UniSoft Corporation Why use XAV? XFSI logo

Validity - the following are invalid:

Interoperability - examples of Non-Interoperability

Security

  • Class file references privileged operation (method) that requires permission, but does not request permission or is not signed
  • Application contains resource that exploits implementation defect in order to insert and execute native code
  • Class file passes null reference or other value to platform class that exploits implementation defect in JVM or API implementation, possibly causing JVM failure or override of JVM security framework
  • Application accidentally or intentionally creates denial of service incident by consuming all resources (CPU or memory) or by saturating return channel with traffic
  • Application contains non-obfuscated class files

Efficiency

  • Application contains class files or members that are not referenced by any execution path
  • Application contains superfluous hash (digest), signature, certificate, or permission files
  • Application contains other data files not referenced by any execution path or defined platform mechanism
  • Application resource contains optional constructs that should not be present or for which universal support is not required

XAV Implementation

Web Interfaces (UI)

  • Enterprise WebObjects (Apple)
Content Analysers
  • J2SE 5.0 Based
  • Selective Native Support via JNI for efficiency
  • No reliance on 3rd party decoders or analyzers; decoders and analyzers written from ground up for detailed content verification and reporting
Database(s)
  • Commercial Cluster Based SQL DB (Microsoft SQL 2005)
Hardware
  • Apple XServer Cluster with redundant 7TB RAID in SAN configuration (UI and content analysis servers)
  • Windows 2003 Enterprise Server Cluster with redundant 3TB RAID in SAN configuration (databases servers)
  • Secure physical and network facilities

XAV Test Suite

Negative Tests
  • A test shall exist for each XAV reportable error and warning and shall produce an appropriate error or warning response
Positive Tests
  • A test shall exist for each defined feature (syntactic and semantic) that is required or permitted by normative specifications and shall not produce an error or warning response, but may produce information or trace respons(es)
Last Updated: September 23, 2007; Copyright © 2006-2007 Extensible Formatting Systems, Inc.
Copyright © 2003-2007 UniSoft Corporation.