Robert Pierce

Indeni is pleased to announce starting October 2019 customers have a new simple method to request development of Indeni automation elements (Auto-Detect and Triage) through the community forum

This is part of our continuing effort to focus on issues that matter most to our customers. In addition, the requests will be open to all members of the indeni community to review and comment on. Leveraging the community will continue Indeni’s tradition of being a leader in crowd source knowledge and thereby building another level of quality in the request. 

Indeni community knowledge request

The request page link is also available starting in Indeni 7.0 in the upper right corner menu.

When submitting a request, we ask the following questions.  The more info in a request, the easier it is for us to develop, but we won’t turn away a great idea just for lack of detail.

1. What is the device type?
<Vendor, OS Version, and other deployment information that the issue pertains to>

2. What is the issue that you want to automate the detection/triage of?
<Explain the issue and how it impacts your business>

3. How can the issue be diagnosed?
<Provide the commands (SSH, API, SNMP, …) that you usually use to troubleshoot the issue and example outputs. Provide details on what values are of interest in the output>

4. What are the Remediation Steps?
<Once the issue is detected, how would you resolve the issue>

5. Are there known ways to reproduce this issue?
<Explain how the issue could be reproduced in a lab situation?

Related Article  We are Launching a New Versioning Scheme

The more information that can be provided will help with the likelihood and time a request is accepted. An example of a request can be found here.

Note: All information submitted in a request is public. Care should be taken to not post confidential information. 

A request life cycle:

New: A request is initially marked as ‘New” and stays in this state until a review begins.
Under Consideration: A request will go to “Under Consideration” when the Indeni product team begins the investigation of the request. 
Accepted: A request goes to “Accepted” if it is deemed feasible and inline with Indeni’s goals. At this point it will be put in Indeni’s feature backlog.
In Progress: A request goes to “In Progress” when development begins. There is no committed timeline when this happens.
Done: When the request is completed and released it will be marked as “Done” with the version it was released.
Declined: A request may be “Declined” anywhere in the process due to issues that may have come up. 

If a request is high priority for your business please contact your Indeni SE for further assistance.

We look forward to getting your requests and making Indeni the tool of choice for your security infrastructure.