How this works
An advice pack is the file a vendor publishes so that its customers can take the vendor's recommendations into their JASCON set: which requirement a product helps with, which clauses, what to configure, and which parameter values the vendor suggests. A pack holds your product as one or more Components and nothing else, so importing it cannot change a customer's requirements, tailorings or assessments. The specification is decision D25; the handbook explains it in chapter 9.7.
- Say who you are: the origin all your identifiers start with, the publisher, the pack and its release.
- Describe the product as a Component and each recommendation as a capability. Loading the catalogue the recommendations refer to is optional; with it you pick requirements and clauses from a list, and clauses and suggested values are checked.
- The panel on the right checks the pack while you type, with the same rules the JASCON app runs when a customer imports it.
- Sign the release with your Ed25519 key, in this page or with openssl, so that customers can tell it comes from you.
- Download the ZIP and publish it together with your public key.
Have an OSCAL component definition already? Import it: each component becomes a Component, each implemented requirement a recommendation, its statements the clauses and its set-parameters the suggested values. A report says what was carried and what has no place in a pack.
Everything stays in this page. Your draft is kept in this browser's storage, your key only in the page's memory: a reload forgets it. To change a published pack, open it, change it and give the release a new version.