Projects
This section outlines the identification, remediation, and monitoring of vulnerabilities across various assets.
The project section offers a comprehensive suite of tools to create, manage, and track your projects from start to finish. Access it through the "Projects" tab from the main menu on the left. This is a central hub for managing security assessments. You can create new projects outlining details like owner, type, and timelines, upload files for analysis, review vulnerabilities, and attach documents. It also offers web, iOS, and Android testing checklists and tracks all project activity.
Creating a Project
To create a new project, click the "Create" button on the top right corner of the screen, above the projects' grid. A new page will appear for you to input project details.
Name: Enter the name of your project.
Type: Specify the type or category of your project. For example: Penetration Tests, Vulnerability scans, Audits, etc.
Infrastructure: Specify the infrastructure of your project. For example: Internal, Staging, etc.
Owner: Select the project owner from the available options. Only users with "Super Admin" and "Security Analyst" roles are listed.
Status: Choose the project status from the available options.
Execution Start and End Dates: Set the start and end dates for the project execution.
Click the “Save Changes” button.
Then, the project is created, and the "Project listing" page is reloaded. You can click on the "Edit" icon or the "Preview Details" button (available under the three dots menu) in the "Actions" column at the end of the project's row to access the project and start working.
Managing a Project
Project Details
To access more detailed information regarding a project, click on the edit icon in the three-dot menu and then the "Preview" button in the "Actions" column at the end of the project's row.
There, you will discover various tabs designed to enhance your project management experience:
Information Tab
The first tab of the project details screen contains general information about the project, such as its name, type, owner, status, etc. This is the first tab that appears when you click the edit icon or the "Preview" button from the description above.
Inputs Tab
The "Inputs" tab serves as a hub for uploading penetration test files. It allows you to import assets and vulnerabilities found by various scanners by uploading the scanner's XML or CSV output file. The system automates the extraction process, creating assets and vulnerabilities seamlessly. To automatically create assets and vulnerabilities:
Click the plus (+) button on the top right corner of the screen, just above the grid.
Fill in the necessary details, then import the scanner output files. You can upload one file at a time.
Remediation Owner: Select, if desired, the person responsible for remediating the vulnerability. This is the owner on the asset level, and it helps with easier remediation tracking.
Risk Owner: Select the person responsible for assessing the severity of the vulnerability and ensuring resolution (e.g., "Security Analyst"). This is the owner of the vulnerability level. The selected risk owner will be assigned to all vulnerabilities and assets from the input.
Network: Select the network if desired. If you don't select a network, the assets found in the uploaded file will be created as "Global Assets".
Click the "Upload" button to save the changes or click "Cancel" to cancel them.
Importing New Vulnerabilities to Existing Assets
When importing scan files to a network, the system will check the existing assets and will import new vulnerabilities to them by respecting the following rules:
Matching Hostname without IP: When the hostname of an imported asset matches the hostname of an existing asset in the selected network, and both assets lack an IP address, the import proceeds. New vulnerabilities are added to the existing asset.
Import to a Network without IP: Vulnerabilities without an IP address will be imported to the selected network.
Adding New Asset with Same Hostname: If there is no local asset with the same hostname as the imported one, the system will add the asset as new, considering the network selection. If only one network is selected or fits into multiple selected networks, the asset is added accordingly.
Skipping Duplicate Asset without IP: If an asset without an IP address shares the same hostname as an existing asset in multiple selected networks, the import process will skip the asset to avoid duplication.
Skipping Import for Unmatched Asset: If multiple networks are selected and an asset without an IP address does not match an existing asset by hostname in any of the selected networks, the import will be skipped.
Vulnerabilities Tab
The "Vulnerabilities" tab provides a comprehensive list of both automatically extracted and manually created vulnerabilities associated with the project. The automatically extracted vulnerabilities are imported from the "Inputs" tab. To manually add a vulnerability:
Click the "Create" button (+) in the right corner above the grid. The following form will be displayed:
Fill in the details.
Scroll to the bottom of the prompt and click the "Save changes" button.
You can also leverage sorting and filtering options for in-depth vulnerability analysis.
Sorting
You can sort your vulnerability list like a spreadsheet:
Click a column header (like name or CVSS) to sort by that column, with an arrow showing up/down in ascending/descending order.
You can even sort by multiple columns - click another header, and a number appears next to it, showing its order in the sorting process.
You can toggle various columns on and off and change their order.
Click on the "Settings" icon [⚙] at the top right corner of the grid. A prompt like the one below will appear.
ii. Click on the "Up arrow" [↑] to move a column to the left of the grid and the "Down arrow" [↓] to move it to the right of the grid.
To save the custom configurations of the current columns sorting and ordering:
Click on the page Configurator icon, then a prompt will appear.
Name the current configuration and click the "Save" button.
You can click the "Make default" button to make the configuration appear every time you visit the "Projects" > "Project Details" > "Vulnerabilities" tab.
You can also load a custom configuration you previously saved from the "Load From Saved Configurations" dropdown list.
Filtering
To filter the vulnerabilities by various criteria, click the "Filter" icon on the top left corner just above the vulnerabilities grid and enter your criteria.
Bulk Edition
To use the bulk editing feature:
Click the checkbox in the upper left corner of the grid to select all vulnerabilities OR Click the checkboxes beside each vulnerability you want to edit in bulk.
Once one or more vulnerabilities are selected, a banner with several buttons will be displayed above the grid:
Click the desired action button ("Bulk Edit Status", "Bulk Edit Owner" or "Bulk Delete")
A pop-up will be displayed, allowing you to execute the change.
Attached Documents Tab
The "Attached Documents" tab is your space to store project-related documents. Keep all relevant documentation centralized for easy access. To upload a new document:
Click on the "New" icon (+) in the top right corner above the grid.
Attach your document.
Click on the "Upload" button to upload the document or "Cancel" to cancel the operation.
By clicking on the three dots menu [ add three dots], you can download, delete, or preview file details such as date, format, upload date, and who added it.
You can again toggle various columns on and off and change their order just like in the "Vulnerabilities" section. To do that, click on the "Settings" icon [⚙] on the top right corner of the grid. Then, a prompt will show up. Click on the "Up" arrow [↑] to move a column to the left of the grid and the "Down" arrow [↓] to move it to the right of the grid.
Similarly to the "Vulnerabilities" section, you can also sort your documents list by clicking on a column header (like "Name" or "Date added") to sort by that column, with an arrow showing up/down for ascending/descending order. You can even sort by multiple columns - click another header, and a number appears next to it, showing its order in the sorting process.
Executive Summary Tab
The "Executive Summary" tab provides a dedicated space to input essential information about the "Project", "Scope", and "Conclusion". Insert relevant information to summarise the key aspects of the project.
Checklists Tab
The "Checklists" tab offers a convenient list of penetration tests specifically tailored for Web applications, iOS, and Android. You can change an item's status to keep track of what has already been executed as a test. You can also change the status of multiple items:
Click the checkbox in the upper left corner of the grid to select all items OR Click the checkboxes beside each item you want to edit in bulk.
Once one or more items are selected, a banner with a "Change Status" button will be displayed above the grid:
Click the button and, in the pop-up, select the desired status.
Jira Integration
You can add a project in Jira as a Jira story. That way, you can also add vulnerabilities in Jira as child issues, and every update on the project or a vulnerability in Kikimora will also automatically appear in Jira. Vulnerabilities can either be added manually or automatically.
To integrate a project with Jira:
Go to the main "Projects" tab from the main menu on the left panel of the screen.
Click on the details of the project you would like to integrate by either clicking on the "Еdit" icon [🖊] or the "Preview" button from the three dots menu [⋮].
Click on the "Create in Jira " button on the right corner of the screen.
Then, a prompt will appear showing you the Jira project that will be used with the ticket title. Click the "Create" button to create the Jira ticket or "Cancel" to cancel the operation.
An info box saying the ticket was successfully created should appear. Then, a "View in Jira" button will appear in place of the "Create in Jira" button.
By clicking on the "View in Jira " button, the newly created story will open in Jira in a new tab with all the details being prefilled.
When a project is updated in Kikimora, it will also be automatically updated in Jira. For example, if you change the status of a project in Kikimora to "Closed", it will be automatically changed in Jira to "Done". If you later decide to open it up again, it will again change in Jira.
Adding Vulnerabilities to a Jira Project
To manually add a single vulnerability to Jira:
Go to the project details > "Vulnerabilities" tab as described above.
Click on the "Edit" icon [🖊] at the end of the vulnerability row.
Click the "Create in Jira" button on the top right corner of the screen.
Then, a prompt showing you the ticket details will appear. Scroll down and click the "Create" button.
An info box showing you that the operation was successful should appear, and you will be redirected to the main project details screen.
Click on the project's "View in Jira" button. You will be redirected to Jira. The vulnerability will appear as a child issue of the project story.
Click on the child issue to view the vulnerability ticket with all the prefilled information.
Any updates made on the vulnerability in Kikimora, such as changes of status, comments, etc., will appear here as well.
Automatic Jira Ticket Creation
You can make all vulnerabilities with a CVSS score higher than a certain amount to be added to Jira as child issues automatically. To do that:
Go to the "System" > "Integrations" section of the main menu on the left panel.
Click on the "Manage" button on the "Jira Software" card and then go to the "Settings" tab.
Click the "Automatic Jira ticket creation" toggle.
Adjust the CVSS threshold above which Jira tickets will be created.
Timelines
The "Dashboard" section from the main menu displays the projects' timelines visually. This gives a quick overview of project lifespans without the need to check each project's details in its Information tab.
Change Logs
The "Change Log" feature provides a detailed record of every action performed by users on the project. Here's how to access and interpret the information in the "Change Log":
Accessing the Change Log:
Navigate to the "Projects" page from the main menu.
In the "Actions" column, click on the "Change Logs" button associated with the desired project.
Change Log Grid:
Upon clicking the "Change Logs" button, a pop-up grid will appear, displaying the following information:
Action Type: Describes the type of action performed by the user, such as creating a new project, updating project details, or other.
Date Stamp: Indicates the date and time when the action was executed.
User: Identifies the user who acted.
Understanding the Change Log:
The "Change Log" is a valuable tool for tracking project activities and user interactions. Each entry in the grid provides insights into the history of changes made within a project, allowing users to review and audit actions.
Deleting a Project
Deleting a project is a straightforward process, and the system provides a secure way to manage project removal. Here's a step-by-step guide on how to delete a project:
Locate the project you want to delete in the project's grid.
Click on the three dots menu [⋮] in the "Actions" column at the end of the project's row.
Click the "Delete" button from the options that appear.
A confirmation pop-up will appear to ensure the intentional removal of the project.
If you are sure about deleting the project, click the "Yes" button.
If you decide not to proceed with the deletion, click "Cancel" to close the pop-up without deleting the project.
Last updated