AI Access Security enables organizations to safely adopt GenAI applications by employees by mitigating the risks posed by inadvertent data leakage in prompts and malicious content in responses. I was assigned the responsibility of managing a team of 3 writers to scope, plan, and deliver the entire documentation set from concept commit to general availability. AI Access Security is built on top of exiting data security services and is thoughtfully designed to leverage existing documentation while detailing use case-centric workflows specific to AI Access Security. 

Highlights

• Discover Risks Posed by GenAI Apps - Demonstrates workflows centered around specific use cases AI Access Security is meant to address. Rather than provide only a generic walkthrough of the dashboard, these procedures are designed to help facilitate the end user's ability to actually use the dashboard filters and achieve a positive security outcome.

• UI Copy Collaboration - My team and I provided all of the UI copy for AI Access Security. This allowed us to facilitate the proper usage of terms across the entire service interface to ensure a consistent user experience. 

• Cody LLM Usage - We used the Cody LLM to deliver AI-assisted documentation for the majority of this documentation set. Exposure to the Cody LLM taught me prompt engineering techniques, increased my productivity, and allowed me to focus on larger project management tasks while still producing high quality and accurate deliverables.  

Enterprise Data Loss Prevention (DLP) is a cloud-based data loss prevention service that uses AI/ML detections to prevent exfiltration of sensitive data. I lead, designed, and authored the documentation set when the service was first being developed from ideation to delivery. I continue to maintain this by documenting new capabilities and enhancing user experience as needed. Service follows an agile development cycle and  I attend weekly product management, engineering, and program standups to keep the team up to date about deliverable timelines.

Highlights

• What's Supported with Enterprise DLP? - Demonstrates thoughtful consideration to user experience by aggregating relevant information into a single page that is easily referenceable. No need to juggle multiple links to know what Enterprise DLP supports. This structure is applied throughout the documentation set. 

• Email DLP - Example of feature  documentation. Procedure to set up has very specific steps that if done incorrectly results in emails not being forwarded to the DLP cloud service for verdict rendering. To ensure a successful outcome, I included an image so the user can validate each step is done correctly. I worked with developers and QA to test, report bugs, and offer UX and UI feedback as I worked with and documented the feature.

• Copilot PoC - Early involvement with Copilot initiatives within the company. Documentation enjoyed improvements based on Copilot efficacy testing such as prompting new topic creation and improving existing ones. I am an active member in prompt engineering bug bash sessions to tune the Copilot.

The Panorama management server is a device configuration management product that also functions as a Log Collector. I inherited this product documentation set when I first joined the company and it sees about 2 million unique visits each year across the multiple supported versions. Working on Panorama requires me to have a big picture considering for how the individual components of the cybersecurity solution work together. I always need to think critical when working on new features or making improvements to consider their downstream impact.

Highlights

• Install the Panorama Virtual Appliance - Example of feature documentation. This required me to installation the Panorama virtual appliance on each hypervisor to validate all procedures and identify any hypervisor-specific behavior that I discovered.

• Panorama Interconnect - The Interconnect plugin allows a Panorama Controller to manage multiple Panorama when managing an extremely large set of firewalls. This plugin and documentation were developed to address the use case for specific customers. This allows the team be very responsive and and author content almost tailor-made for the users this was developed for. 

• Team Lab - I built an internal lab for myself and my team to use to give us reliable access to developer builds rather than relying on others for access. I have a PCAP generating running traffic through the lab firewalls so others can learn to write Security policy rules and read logs. I maintain this lab with multiple firewall versions running so we always have access to supported PAN-OS software. This also allowed me to validate and improve any documentation used during setup.