Inventory & Constellation
Identify supported systems, connected sources and action/access paths.
System-level assurance, action and access evidence, deterministic evaluation and review artifacts form the HAIEC platform. Independent developer tools and specialized utilities address narrower questions without pretending to prove the entire operating system safe.
This grouped concept is a product navigation aid, not proof of a mandatory lifecycle.
These are connected modules of one platform, not unrelated subscriptions. Begin with your source and question; add qualified evidence where it changes the decision.
Identify supported systems, connected sources and action/access paths.
Source-visible security findings, technical action paths and coverage.
Compare authority, capability and qualified evidence with explicit limitations.
Review scoped decisions with accountability and supporting records.
Follow supported connected sources and runtime observations.
Return to exact evaluations, provenance and verifiable artifacts.
Static security analysis of AI applications and agent implementations.
Explore AI AppSec →Deterministic checks for cross-tenant boundary risks in MCP implementation.
Explore MCP security →Pattern-based selected prompt/input/output checks. Not full-model safety proof.
Explore LLMVerify →PR Compliance and SDK usage tracking, each with its own supported output.
Specific logs, questionnaires and evidence prompts. Framework mappings are not certification.
Connection-dependent safeguards and monitoring. No general-purpose automatic enforcement claim.
| Question | Path | What the output does not establish |
|---|---|---|
| What can this agent cause? | HAIEC Platform | Unknown evidence never becomes passed control. |
| Is the application code secure? | AI AppSec | Static findings do not prove execution. |
| Can MCP handling cross tenants? | MCP Tenant Isolation | Static checks do not prove every runtime boundary. |
| Does text match selected risk patterns? | LLMVerify | Pattern matches do not certify AI safety. |
| Do we need logs or compliance gap prompts? | Specialized tools | Logs and checklists alone are not platform assurance. |
If your client supports remote MCP servers, connect HAIEC with a securely stored API key. Then say Run HAIEC AI Assurance. Your agent checks readiness first; the preflight determines the eligible next action. This is not automatic repository access or evidence of a completed scan.