> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/about-iz-eye.md).

# About IZ Eye

## Introduction

**`IZ Eye`** continuously monitors configured environments and reports whether the deployed applications are identical. This helps organizations see whether the code in promoted environments is consistent and the DevSecOps process is working as expected.

#### Supported Platforms <a href="#supported-platforms" id="supported-platforms"></a>

\
IZ Eye discovers and scans deployed applications on the following platforms. Each application type is listed in the IZ Eye menu under its platform, and only the types granted on your licence are shown.

| Platform              | Application types                                                                                                                                                                                                                               |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Anypoint Platform** | Mule Projects, APIs, API Instances                                                                                                                                                                                                              |
| **Azure**             | Azure Logic Apps, Azure API Management, Azure Function Apps                                                                                                                                                                                     |
| **AWS**               | AWS Lambda, AWS CloudFormation, AWS Step Functions, AWS API Gateway, AWS ECS, AWS RDS, AWS Load Balancer, AWS Secrets Manager, AWS CloudFront, AWS DynamoDB, AWS SQS, AWS SNS, AWS EventBridge, AWS CodePipeline, AWS CodeBuild, AWS CodeDeploy |
| **Others**            | Salesforce Apex, Kubernetes                                                                                                                                                                                                                     |

### Continuous Runtime Monitoring

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FU5ndBaPwD1WB6WgGFCxF%2Fabout.png?alt=media&amp;token=751d5987-fc74-4de3-af92-a9954b325482" alt=""><figcaption></figcaption></figure>

Runtime code analyzer tool like **`IZ Eye`** fills this gap by continuously scanning any changes to all the environments based on the configuration and can intelligently determine when new code or API has been deployed to any of the servers.

It can identify whether the same code in dev environment has been promoted to Staging and Production environments or whether its a modified/new code deployed to the environments.

It analyzes the code deployed if new and alerts based on any new vulnerabilities introduced with the deployment - so that even if the static code analysis didn’t capture the issues or if the process is by passed, it will capture and provide up to date state of the organization clearly.

This helps make sure that the organization can have a reliable way to check the runtime state of the estate - rather than just assuming that process works or to miss checking for any unauthorized deployments or changes at all!

### Keep Compliance Current (KCC)

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtFTwu4XPYwOxQ9sP8k81%2Fkcc.png?alt=media&amp;token=081a2085-d9b5-4d23-8b98-6a36bb029363" alt=""><figcaption></figcaption></figure>

When we have deployed hundreds of APIs/Applications which utilized various java packages or modules, in built connectors, custom connectors and libraries, we encountered two main types of changes to the security profile:

1. Critical vulnerabilities like Log4j vulnerability are discovered very frequently - and as part of company policy they want to make sure that such vulnerabilities are quickly identified and fixed both in standard components and custom components.
2. If a company guideline change (for example - allowed authentication methods or connectivity methods to a specific API/system changed from earlier policy to a new one or API specification guidelines are changed) - one would like to identify the technical debt easily.

Whenever guidelines change like this and they had hundreds of applications and APIs, the usual way of scanning each and every application/API is a huge laborious process. How do we get around this issue?

With a tool like IZ Runtime analyzer, whenever company adds or modifies their policy guideline, this will trigger a complete re-analysis of the entire affected infrastructure applications/apis - so that organization readily obtains updated report on the compliance of the organization.

Any application which was compliant under the old guideline or rule set, could be either compliant, partially compliant or non-compliant according to the new set of guidelines.

This reduces the huge overhead on the Dev Sec Ops team to re-trigger analysis of the entire application code base to analyze things - as well as capture rogue/bypassed applications according to the new guidelines to always keep the compliance current.

In summary, IZ Runtime analyzer provides ability to rescan the entire application infrastructure so that compliance of the organization remains current no matter the frequency or type of guideline change.

### Coverage Analysis

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FyIch1Umd1Ktd2oeKT8YW%2Fcoverage_analysis.png?alt=media&amp;token=fe25d0d9-3b37-4c56-b2ff-392f2c6c532f" alt=""><figcaption></figcaption></figure>

In **`IZ Eye`**, not only component level code/specification is scanned with issues and metrics captured, it provides a capability of linking the assets across the entire estate.

This enables easy way of analyzing the compliance data in one shot - whether you would like to understand it at component level, summary level or based on custom tag level!

This enables you to truly have a compliance dashboard specific to whatever level of data that you desire - and analyze the risk associated with issues discovered by the tool!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/about-iz-eye.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.