Reviewing Wickr documentation we determined a Web Interface Integration would do the trick for us. The process was well documented, and we were able to prototype a solution that met our initial set of requirements. From here we moved to a production-based setup that handles a few things for us. It should be noted that all of the items below operate utilizing the Web Interface Integration, meaning we were able to share the core code between the varying projects to get the necessary information into the respective Wickr rooms.

1. Users utilize existing process (JIRA) to create RFIs. We wrote code that interacts with the JIRA API to pull out these RFIs, format them accordingly and subsequently securely send to a dedicated Wickr Room. The participants in this room utilize Wickr as an integral part of their workflow and are able to take and act on the information more easily, saving time, gaining efficiency and getting the information back into the requestor’s hands more quickly. Next steps for us here is to review the ZenDesk Integration and see how we can modify it to work more seamlessly with JIRA so we can decrease the amount of code/moving parts.
2. While we utilize commercially available log collection, analysis and alerting products there are just some things we deemed important enough to also push to a dedicated Wickr room. These alerts, which we have fine-tuned, allow our folks to quickly triage and resolve issues quicker.
3. In an effort to get information disseminated out faster to various groups, we decided to leverage the same code to send both daily and weekly notifications and statistics on various malware families we are tracking. This provides our people with the situational awareness they need as we collect. Next steps for us here is to review the FileBot/attachments to quickly and securely send files.