Would it be possible, or make sense, to develop a Skillet Pathway (or Pathways)?
Related to my other question, once the Day 1 Configuration is run, what next? Maybe there is a defined path, or several different paths, that would identify use cases and the proper skillets to implement...would this be feasible?
Is this something that would be used, or would be helpful?
That's a great question, and something we are working towards. Right now, the Day 1 (IronSkillet) configuration is intentionally vague and use case agnostic. Ideally, we will have skillets for multiple specific use-cases. I.E. branch office with HIPPA requirements would have a pathway like Day1 -> Branch office -> HIPPA skillets. This should get the user to 85%+ of the best practice configurations.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!