
A standardized container associating digital files with the detached signatures or time assertions that apply to them.
An Associated Signature Container (ASiC) is a standardized digital package linking data files with associated signatures or time assertions. It uses a ZIP-based structure defined by ETSI EN 319 162-1; merely renaming an ordinary ZIP file does not make it a conforming ASiC container.
The distinction concerns container structure, not a universal difference in legal strength. A filename or extension alone does not establish that the contents conform or that every file has been signed.
The container keeps payloads and their signature relationships together. It can use CAdES or XAdES signature structures and relevant time assertions. The exact objects covered must still be checked; packaging does not automatically prove identity, authority or qualified-signature status.
Extracting a document can make it readable, but that individual file is not necessarily the complete evidence package. Preserve the container, referenced objects and supporting material needed for validation.
An ASiC package can carry material supporting later signature validation. Keeping a ZIP-based file is not, by itself, a guarantee of long-term verifiability. Validation still depends on its signatures, trust information, time evidence and applicable preservation process.
A Common Case: Receiving an EU partner’s signed package
Consider a Washington consulting firm receiving an ASiC package from an EU partner. Keeping the complete container allows the team to review the covered files and associated evidence. Extracting a readable agreement alone may leave that review incomplete.
No. ASiC requires a defined structure and relationships between data and signature or time-assertion objects; changing the extension is not enough.
It associates one data file, but that file can itself be an archive. Check the actual container and its covered objects.