Stanton Hoener

Innovative and detail-oriented Splunk Software Engineer with extensive technical experience in testing, evaluating, designing and implementing solutions. Proven track record updating current software systems, making improvement suggestions, collaborating with analysts and designers, testing applications, writing training manuals, and making sure projects are completed in time and within budget. Known for programming skills, creativity, attention to details, time management, and teamwork. Strength in creating an inclusive culture with strong communication and teamwork that benefits the entire organization.

• Technical Team Lead for seven Splunk Software Engineers
• Build on-prem/AWS Splunk Hybrid Environment starting with 1TB indexing per day up to final size of 36 TB data indexing per day, 1.2PB storage, 84 clustered indexers, 8 search head clusters, and 7,000 input forwarders.
• Splunk Enterprise Security,” Installed and built Splunk premium app with inputs using CIM formatting. This allowed Security Analyst and Threat Hunters to span notables events across multiple sources allowing stream lined detection of threats.
• “Splunk IT Service Intelligence (ITSI),” Installedapp to trace company business flows. Allowed upper management to see and measure the impact of flow disruption.
  “Splunk add on for Phantom” Installed and upgraded, allowing automation directly from Splunk Security Events, reducing security reaction time.“Splunk frozen data backup,” devised AWS Glacier automation, backup and recovery protocols to meet regulatory 7 year data retention policy. Using the low cost of Glacier as compared to regular disk space saved the company millions of dollars as the data aged to 7 years of retention.
• “Splunk Enterprise Core Infrastructure.” Installed and upgraded, as the Splunk requirements increased so did the Infrastructure.
  Worked multiple times (120 hours) with “Splunk Professional Services” as part of the team to perform Enterprise upgrades. This allowed unique insights into an large Enterprise Design of Splunk which allows remote automation and ease of maintenance. This also allowed me to perform upgrades on my own.
• Splunk inputs from Rsyslog, 8 server cluster specifically built to pull Palo Alto logs into Splunk.
• Splunk inputs Syslog-ng, 8 server cluster specifically built to pull network traffic into Splunk.
• DBconnect, installed and upgraded allowing of Databases to be pulled directly into Splunk.
• Developed a Yearly Splunk wellness review, This involved defining benchmarks, and comparing them over time to keep the Splunk Environment healthy and performing at Peak efficiency.