AppControl Docs
  • Introduction
  • Overview
    • Features
    • Product architecture
      • AppControl Repository
      • Policy Checks
    • Initial set up
      • AppControl User
      • Install package
      • Configure system
      • Add apps
      • Add users
      • Give permissions
    • User Roles & Access
    • Getting Started
      • Platform Administrator
      • App Owner
      • App Administrator
      • Developer
  • Dashboards
    • Platform
    • Alerts
    • App
      • Log Rule
    • Policies
      • Compare Revisions
    • Releases
      • Create Release
    • Tasks
      • Task Assignment
      • Task Details
    • Insights
      • Components
      • Reports
      • Users
      • Logs
  • Administration
    • Policies
    • Pipelines
      • Approval
      • Backup
      • Build
      • Call API
      • Check Policy
      • Deploy
      • Deploy Configuration
      • Notification
      • Start / Stop
    • Tasks
    • App Groups
    • Access Groups
    • System
      • Accounts
      • Notifications
      • System Status
      • System Logs & Tools
      • System Configuration
      • Repository
        • Log Solution
      • Product License
      • Management API
      • Mendix Configuration
    • Feedback
  • Checks
    • APIs
      • Published APIs must use authentication
    • App
      • Project security level
      • Project security enabled
      • Demo users enabled
      • Anonymous users enabled
      • Strong password policy
      • Default admin username changed
      • Anonymous user access restricted
      • Default admin user restricted
      • Use strong hash algorithm
      • Check user role security for consistency
      • Restrict users to a single session
      • Perform strict page URL checks
      • Project naming standards
    • Components
      • Components with vulnerabilities
      • Mendix runtime version age
      • Mendix runtime support status
      • Non platform supported components
      • Max component age
      • Average age components
      • Use latest version of Marketplace module
      • Use latest version of Marketplace widget
      • Use latest version of Mendix
      • Limit number of Java libraries
      • Limit number of widgets
      • Use minimum Mendix runtime version
    • Constants
      • Do not expose constants to client
    • Development
      • Last commit to production
      • Last commit to project
      • Project documentation standards
      • Project organization standards
      • Project logging standards
    • Domain Model
      • Default member access rights restricted
      • Use read only attributes in XPath constraints
      • Anonymous users can only change own data
      • Anonymous users cannot change unlimited length strings
      • Domain model standards
      • Anonymous user access restricted
      • Naming standards - Domain Model
      • Documentation standards - Domain Model
    • Enumerations
      • Naming Standards - Enumerations
    • Microflows
      • Incorrect date format
      • Incorrect empty string check
      • Empty variable used
      • Apply entity access when generating documents
      • Use inherited entities from System module
      • Web service calls with templates should be escaped
      • Naming Standards - Microflows
      • Logging Standards - Microflows
      • Documentation Standards - Microflows
    • Pages
      • Attributes in data views should be editable
      • Naming Standards - Page Flows
      • Documentation Standards - Pages
  • Support
    • Docs
    • Feedback
    • Tickets
    • Releases
    • System Status
    • User Details
Powered by GitBook
On this page
  1. Dashboards
  2. Insights

Reports

PreviousComponentsNextUsers

Last updated 3 months ago

The Reports tab displays all environments detected by AppControl in all of your hosting platforms. For each environment, if the deployed revision has been analyzed, a complete app health report is available. If AppControl does not have sufficient access to the app, or the deployed revision has not yet been analyzed, the message 'no deployed app' will be displayed.

You can download a PDF version of the app report by clicking on the 'download PDF' link. Note: This feature must be configured first by your platform administrator from the feature settings tab in the page.

After clicking on 'view report' the following information is available:

App Info
  • Name. The name of the app.

  • Mendix App ID. The Mendix App ID for this app (also known as a 'project ID').

  • Hosting platform. The hosting platform that AppControl detected this app on.

  • App repository. The app repository that this app is using to store it's project files.

Environment Info
  • Name. The name of the environment.

  • URL. The URL of the environment.

  • Mendix Version. The Mendix version in use by this environment.

  • Model Version. The model version that is currently deployed to this environment.

Policy Compliance

The policy compliance tile shows a summary of the results of the policy check for the revision that is deployed to the selected environment. For each policy check category the following information is displayed:

  • Total check results. The total number of failed check results. (check result = unique combination of check type and specific element)

  • Percentage. The percentage shows the percentage of checks (=check types) that were configured for this scorecard that passed (= did not generate any failed check results).

  • Star rating. The star rating is a simple visualization of the percentage of checks that passed where 100% = 5 stars.

Vulnerable Components

The vulnerable components tile shows a summary of the components used by the currently deployed revision that have known vulnerabilities. For each vulnerable component the following information is displayed:

  • Component Type. The type of component.

  • Name. The name of the component.

  • Version. The component version.

  • Vulnerabilities. The list of known vulnerabilities.

Security Risks

The security risks tile shows a summary of the security risks found in the currently deployed revision. Security risks represent all security type policy checks that have a high risk that failed. For each detected risk the following information is displayed:

  • Severity. The severity level of the risk.

  • Risk ID. The policy check ID of the risk.

  • Security Risk. A brief description of the risk.

  • Element Type. The type of app element that is affected by this risk.

  • Vulnerabilities. The number of vulnerabilities of this type that were found in the app.

System Configuration