Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
ASILO: profile and evolution¶
A profile applies the method to a context. This current template documents profile fields; it approves no technical profile and imposes no particular number of rings. Informative translation.
| Field | Declaration |
|---|---|
| Identity | Name, revision, status and maintenance responsibility. |
| Scope | System, assets, actors, effects, conditions and exclusions. |
| Model | Responsibilities, dependency direction and exceptions. |
| Authority | Identity, resources, operations, validity, revocation and applicable delegation. |
| Mechanisms | Concrete controls, configuration and host boundaries. |
| Evidence | Scenarios, tools, versions, results, limits and provenance links. |
| Evolution | Compatibility, transition, retirement and exception review. |
Numbering belongs to the profile. If sources assign different numbers to the same responsibility, record the contradiction instead of renumbering an accepted rule. Named responsibilities help avoid treating numbers as trust or privilege.
A new operation, dependency or integration revisits threats, authority and effects. Exceptions identify responsible person, reason, scope, duration and review. Incompatible changes preserve a documented transition.
The method remains independent of providers and implementations. Each implementation documents installation, API, operational configuration and software results. Declaring a profile does not demonstrate that its controls are running.