-
Notifications
You must be signed in to change notification settings - Fork 1
Style Guide
Mission Control is a Trend game interface that allows us to create events where participants get hands on experience with Trend Micro products and real-world scenarios in a fun and interactive way.
This purpose of this guide is to provide Challenge Builders with instructions and advice on how to structure the wording for your challenge that is presented in the game board to a player.
For information on how to build a challenge, please see the Challenge Build guide.
The Challenge Name is used by the backend team to identify the challenge. This is not visible to the public. Challenge names should be the application or service you are highlighting and an indicator if it's a Day 1 challenge or a Day 2 challenge.
Example: Application Security – Day 1
Example: Workload Security API – Day 2
Each challenge will consist of one or more tasks. If you want the player to complete multiple steps, consider dividing it into separate, logical tasks so you can verify their progress along the way.
Example: You want the player to create a Cloud One account, add an AWS cloud connector, create an EC2 instance, deploy the agent and then add a policy to block a port on the firewall. This could be broken down into tasks. One way to do this might be:
Task 1 – The player creates the Cloud One Account and adds the AWS connector then creates the server and adds the agent. You can use a verification button to check to make sure the server has the agent installed and is managed.
Task 2 – The player then enables the firewall and sets it to block the port you specified. You have another server trying to infiltrate the box on that port. Use the verification button to check to make sure the attack is being blocked.
The name of your task is visible to the player and should be something interesting and engaging. It can relate the story you are telling in your task description. Remember his a game and should be fun!
The description should tell the player what is the scenario they are facing. This should be a real-life situation and something they can relate to or a problem that a customer might face. Make the scenario as real as possible to highlight the benefits of using Trend products and services to solve them. You should include the name of the main Trend product or service that the player will use. Optionally, you can add a company name or industry or any other details that might make the challenge more relatable or more real.
Example 1: Your company is concerned that one of its S3 buckets may contain malicious objects and is being used for attack purposes. Use Trend Micro Cloud One File Storage Security to scan your S3 bucket to find out which files are malicious.
Example 2:To reduce cost and increase scalability, your company has deployed their first serverless application. While serverless functions can be more secure than traditional platforms, they are not impervious to exploitation. Your company chose to secure their serverless applications with Application Security.
In the details section, you will describe for the player what steps you want them to accomplish. Optionally, you can number the steps to make them more logical if there are several parts to the task.
Example: Set up SNS in your C1WS account.
- Login to your Trend Micro Cloud One account
- Set up forwarding of system events from your C1WS to Amazon SNS. You can check the key/secret key/Cross Account Role ARN in the "Credentials" section.
- Test the connection with the "Test credentials and send notification" button.
- Click the Verify button to verify the Amazon SNS setting.
The notes section is optional but normally contains things that you know may not be straight forward to the player. Often times you will see a note in the task that talks about why we use Service Catalog in our challenges instead of having the player use Cloud Formation templates that are part of most Trend services.
Example: Several Trend Micro products use Cloud Formation templates to allow users to easily accomplish tasks such as connecting their AWS accounts to our service. However, in some environments, including the AWS environment provided with these challenges, permissions for the player are limited or not granted by design. Several challenges utilize Service Catalog products to accomplish tasks that the player won't have access to in order to complete the task.
Sometimes players will need a little assistance if they get stuck during a challenge and they will need to take a hint. For each challenge, you should include 2-3 hints. Keep in mind that the player will lose points for taking a hint so each hint should be valuable. The last hint should be a complete walk through of the entire task.
Below is a list of things to look for or things to avoid when writing a challenge.
| First instance | Subsequent use |
|---|---|
| Trend Micro Cloud One | Trend Micro Cloud One |
| Trend Micro Cloud One – Workload Security | Workload Security |
| Trend Micro Cloud One – Application Security | Application Security |
| Trend Micro Cloud One – Container Image Security | Container Image Security |
| Trend Micro Cloud One – Network Security | Network Security |
| Trend Micro Cloud One – Conformity | Conformity |
| Trend Micro Cloud One – File Storage Security | File Storage Security |
| Trend Micro™ Deep Security software | Deep Security |
Do not use acronyms or abbreviations in place of the product names listed above.
Do not use "Cloud One" on its own (it's always "Trend Micro Cloud One" for legal reasons).
Use > in UI navigation paths, where possible.
Example: Go to Computers > Smart Folders.
Spell out on first use in the topic, unless the term (example: HTML and DNS) is obvious to the target audience.
Don't use internal acronyms, such as C1 or WS. Product names shouldn't be acronyms for US trademark reasons.
Use numerals, not spelled out, even for 1 to 10.
Use a monospace font. Use < > to indicate variables in commands. Don't format text with hard line breaks (Enter/Return). Example:
ALTER ROLE <username> CREATEDB CREATEROLE;
Why? Line endings in wrong places violate programming syntax rules. If user's copy-and-paste from your command line/shell script/compiled code, it won't work.