Internal awareness paper on Wiz at CMS
Summary
Freelancer Client is hiring: Internal awareness paper on Wiz at CMS.
Location: Remote
Wiz is a cloud security and risk-detection platform that has been enabled across all MPSE accounts at CMS, but adoption is uneven and many internal teams aren't aware of what it does, what it can replace or complement, or how to get access. We need a short paper (1-3 pages) that introduces Wiz to internal CMS technical staff, explains its core capabilities, and gives readers a clear path to getting started.
Requirements:
• Length: 1–3 pages, 600–1,500 words
• Format: Microsoft Word (.docx)
• Voice: neutral, authoritative, non-salesy
• Structure: light headers only, otherwise continuous prose
• Once complete, I’ll review for accuracy, clarity, and consistency of terminology before sign-off.
• Attached is a template because this is for the ISSO Journal
Skills: Cloud Computing, Technical Writing, Report Writing, Ghostwriting, Article Writing, Content Writing, Documentation, Cloud Security, Technical Documentation, Microsoft Word
Budget: $30–$250 USD
Source: Freelancer Client via Remote / Online. Apply on the source website.
Original
Project overview
Wiz is a cloud security and risk-detection platform that has been enabled across all MPSE accounts at CMS, but adoption is uneven and many internal teams aren't aware of what it does, what it can replace or complement, or how to get access. We need a short paper (1-3 pages) that introduces Wiz to internal CMS technical staff, explains its core capabilities, and gives readers a clear path to getting started.
Audience
Internal CMS technical staff who may not yet use Wiz — cloud engineers, application security teams, developers, and platform owners across MPSE accounts. Assume readers are cloud-fluent (familiar with AWS, IAM, Kubernetes, etc.) but have no prior exposure to Wiz specifically.
I need a concise, well-structured product description that my internal team can rely on as a single source of truth. The final document should run 600–1,500 words (roughly one to three pages) and be delivered as a .docx file.
Please keep the tone plain and professional—informative rather than promotional. Use short section headers sparingly so the file is easy to scan, then let clear prose carry the details. Think of it as briefing smart colleagues who already understand the industry landscape but need the product’s specifics laid out cleanly.
Core requirements
• Length: 1–3 pages, 600–1,500 words
• Format: Microsoft Word (.docx)
• Voice: neutral, authoritative, non-salesy
• Structure: light headers only, otherwise continuous prose
Once complete, I’ll review for accuracy, clarity, and consistency of terminology before sign-off.
Attached is a template because this is for the ISSO Journal
Location & Details
Apply on source →About this listing
This remote opportunity was imported from Freelancer and is shown here for discovery. To apply, follow the link to the original posting.