axigetik: AI System Impact Assessment
Cabahu · Cybersecurity & IT
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
An artificial intelligence system impact assessment, or AI impact assessment (AIIA) is by far the most substantial piece of work that you will undertake in the development and implementation of an ISO/IEC 42001:2023 conformant artificial intelligence management system (AIMS).
ISO/IEC 42005:2025 provides guidance on how and when to perform AIIAs. An AIIA must be completed at the very beginning of the AI lifecycle, prior to inception or use of the AI technology, and must also be regularly updated and maintained throughout the system’s lifecycle / whilst the system is in use.
Show the rest of the publisher’s description (17 more lines)
But whether you are chasing ISO/IEC 42001:2023 or another AI certification, or simply investing in an structured approach to inventory and analysis of AI in-use in your organization, an AI System Impact Assessment can provide significant value.
We can help with:
## Develop AI System Impact Assessments
There is some flexibility around how AIIAs are conducted; the best approach will depend on the specifics of your organisation.
The basic approach to conducting an AIIA is similar to an data systems inventory and audit – we need to gather and document information in line with each section of the assessment. Unlike an audit, there is no need to gather evidence to support the assessment, which makes process slightly easier and more efficient.
How we can help ...
- Confirming your position with regard to AI systems - are you a developer/producer or a user/consumer or both ?
- Determining the most relevant and useful approach to grouping or splitting AI system impact assessments
- Identifying the most useful template for AI system impact assessments (there are a number of commonly used variations - ISO/IEC 42001:2023 isn't prescriptive, but ISO/IEC42001:2025 is a good default)
- Facilitating the gathering of information to complete the AI system impact assessment
- Developing the draft AI system impact assessment itself - typically a very substantial document
However, it is important to remember that if you are using AI systems for different outcomes and with different associated risks, you may need to conduct multiple separate assessments of those systems.
## Review and Update AI System Impact Assessments
We can also work with you to review and update existing AI system impact assessments, including using historical and overlapping documentation to make the end-to-end process more time and cost efficient, and cross-validate the documentation against systems in use using our extensive engineering knowledge.
We usually suggest a bi-annual / 6 monthly review of AIIAs, owing to the speed at which AI systems are incrementally changed and improved.
##### Specific AWS Services Addressed
An AI System Impact Assessment AI is not AWS specific and will capture a wide range of information across any/all cloud and on-prem AI services and providers. If you have a significant AWS footprint, including AI services on Sagemaker (including Studio, Custom Models, Hyperpod, Inference, MLflow), Bedrock (including Nova & Agentcore - Runtime, Gateway, Memory, Browser Tool, Code Interpreter, Identity, Observability), open source agent frameworks (eg Strands, LangGraph, CrewAI), other foundation model providers accessed via Bedrock (eg OpenAI, Google Gemini, Anthropic Claude, Meta Llama, Mistral, Cohere) or older AI services such as Comprehend, Kendra, Lex, Personalize, Polly, Rekognition, Textract, Transcribe, Translate we have specific expertise and experience in designing, implementing and operating and documenting these solutions and the wider AWS security and compliance services wrapepd around them (such as Organizations, Identity & Access Management, Config, CloudFormation, Control Tower, Security Hub) to ensure you gain maximum leverage in documenting your AI System Impact Assessment.
Highlights
Highlighted by the publisher on AWS Marketplace.
Extensive engineering experience in designing, building, operating, maintaining AI systems of different types (from expert systems, neural networks, statistical natural language processing, information retrieval, big data, deep learning, transformers, LLMs, agentic AI)
Our staff are certified implementers and auditors across multiple AI security and compliance standards
We bring specific expertise and experience in design, implementation and operation of AWS AI services
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment · as of 2026-08-29
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.

