> For the complete documentation index, see [llms.txt](https://docs.devarmor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devarmor.com/modules/threat-modeler/verify-application-attributes.md).

# Verify Application Attributes

After describing the application, you can review and validate threat model inputs

After providing the initial inputs to the threat model, DevArmor distills specific information that is required to perform a threat model. In the "Decompose" tab, you can review this information, make any changes, and approve them.

This typically includes attributes like:

* Business criticality and data sensitivity of the application and its data
* Authentication and access-control methods in use
* The actors (users, services, external systems) that interact with the application

Correcting an attribute here is much faster than correcting it after DevArmor has generated architecture and findings from it — this step exists so a wrong assumption doesn't propagate through the rest of the threat model.

Once you approve these attributes, DevArmor generates the application's [architecture](/modules/threat-modeler/architecture-and-diagrams.md) and moves on to identifying threats.
