Skip to main content

WIZ Release Notes

1. New Tenant Creation (21st November 2023)​

Feature Requirement:​

Creation of a new CloudLabs tenant to store the test templates.

Implementation:​

Created a new WIZ Content tenant to store the test templates.

Steps For Changing the Tenant:​

Go to the WIZ tenant as highlighted in red. Select the dropdown option, and you should be able to see the WIZ content tenant (as shown in the screenshot below).

2. Power-BI reports​

2.1 Subscription Count (24th November 2023)​

Feature Requirement​

Number of Subscriptions Available for all the three clouds.

Implementation​

Created the PowerBI report for the available and unavailable subscriptions in all three clouds.

Steps to check available and unavailable subscriptions in the PowerBI report​

  1. In the Admin Portal go to the Reports section and click on “Admin”.

  2. Choose the Subscription Count page, here you will be able to check on the availability based on the subscription group name and the cloud platform.

2.2 Cloud Spend Report (28th December 2023)​

Feature Requirement​

Cloud Spend report for All Three clouds.

Implementation​

Modified the cloud spend based on 3 different clouds. Bifurcation is based on Month, tracks, and users.

Cloud Spend Report​

2.3 Sign-in Report (22nd January 2024)​

Feature Requirement​

Sign-in details of the custom portal

Implementation​

Implemented the Power BI report for the sign-in details in the custom portal.

Steps for checking the Sign-in Report​

Go to the Reports section, select Login History, and view the logins organized by time, date, user names, and domains.

2.4 Validations report (27th February 2024)​

Feature Requirement​

Validation status for User reports.

Implementation​

Added a separate column called User Reports to check the validation status.

Validations report​

In the "Validations" column, determine the ratio of validations completed to the total number of validations provided.

Once all validations are successfully completed, the status will be marked as Complete. If some validations are only partially completed, the status will indicate Incomplete. If no validations have been completed, the status will be labeled as Not Validated.

3. Clean up script (26th November 2023)​

Feature Requirement​

Implement the attendee resource clean-up based on the below list.

  1. Connector
  2. Dashboard
  3. Dashboard Widget
  4. Outpost
  5. Cloud Configuration Rule
  6. Host Configuration Rule
  7. Control
  8. Ignore Rule

Implementation:​

  1. Developed the API calls for the cleanup of the resources in the Wiz Portal.

4. Lab Guide Preview (11th Dec 2023)​

Feature Requirement​

Enable user-friendly features for previewing the lab guide before launching the lab in the custom portal.

Implementation​

Added a new tab for a preview button in the lab Catalog view under the custom portal.

Steps for enabling the lab preview option​

  1. In the Admin Portal, navigate to the templates section and click on the edit option for a specific template.

  2. In the template, enable the checkbox for Enable Lab Preview.

  3. Click on the SUBMIT button to save the changes.

  4. Once we have successfully saved the preview option. Navigate back to the On-demand Labs page, edit the respective ODL, and select the Enable Lab Preview option.

  5. Add the Preview URL (Master Doc link for the lab guide) and click on submit.

  6. Navigate to the Custom portal (https://wiz.cloudlabs.ai) and click on Login/Sign Up.

  7. In the Catalog section, choose the lab for which you wish to preview the lab guide.

  8. Click on Preview to view the lab guide.

  9. The lab guide preview is accessible within the portal.

5. Lab Guide Updates (11th December 2023)​

Feature Requirement​

Capability for full-screen view of the image in labguide.

Implementation​

Implemented a feature allowing users to view images in full-screen mode.

Steps for checking the Lab guide updates​

  1. Go to the lab guide page and select the respective image that you wish to choose.

  2. After selecting the image, it will appear in full-screen view, as illustrated in the image below.

6. Catalog View (11th December 2023)​

Feature Requirement​

As more labs are added to the catalog view, the display becomes crowded, making lab titles difficult for users to read.

Implementation​

  1. The issue is fixed by decreasing the font size of the title in the custom portal.

  2. Also provided the character length (54 characters) for the custom portal to view the full name.

Steps for checking the Catalog View​

Note: Spektra supports 54-character limit for headers. If you need any further modifications, please reach out to Labs-support@spektrasystems.com

7. Lab Guide View (11th December 2023)​

Feature Requirement​

Rendering of bold text in Chrome browser on MacBook.

Implementation​

Addressed issues related to bold text rendering in Chrome on MacBook.

checking the Lab guide view​

8. SAML Mapping (8th January 2024)​

Feature Requirement​

  1. Need to make the API calls for creating the WIZ project and assign the roles to the ODL users.
  2. Create a new custom handler that can map to another tenant, where Cloud Labs will be adding the users and assigning the specific permissions that are passed through the custom handler.

Implementation​

  1. CloudLabs will be creating the User to access the CSP and Wiz.
  2. CloudLabs will add the user to a specific group based on the custom handler inputs.
  3. When a user is granted write permissions, a new project will be created, and the user will be assigned to that group. Additionally, a new AAD group will be created, and the user will be added to that group.
  4. If the user is assigned with read-only permission, the user will be added to the existing project and existing AAD group.
  5. After the Lab is finished, if the user possesses the appropriate writing permissions, proceed to delete the AAD group along with the newly established project associated with the user.
  6. If the user has read-only permission, then the user will be removed from the AAD group and the project.

Steps for assigning the Permissions​

To assign roles to the user with either Read-only or Write permission, the following steps should be followed:

  1. In the Admin portal, we need to select the templates section.

  2. Click on Edit Template.

  3. In the Custom Handler section, click on the +ADD button.

  4. In the Custom Handler Section add the below inputs and click on submit.

    Custom Handler: WIZ_HANDLER

    Input Parameter: https://experienceazurecloud.blob.core.windows.net/custom-handlers/wizlabs_global_contributor.json

    Is Active: True

Note:: If the "Is Active" button is not set to true then custom handler permissions will not apply.

Types of Input Parameters​

  1. Wiz_Ctf tenant with Global contributor: https://experienceazurecloud.blob.core.windows.net/custom-handlers/wizctf_global_contributor.json

  2. Wiz_Labs tenant with Global Contributor and Global incident analyst: https://experienceazurecloud.blob.core.windows.net/custom-handlers/wizlabs_global_contributor_response_analyst.json

  3. Wiz_Labs with Global Contributor and Project Admin: https://experienceazurecloud.blob.core.windows.net/custom-handlers/wizlabs_global_contributor_project_admin.json

  4. Wiz_Labs with Global Contributor role: https://experienceazurecloud.blob.core.windows.net/custom-handlers/wizlabs_global_contributor.json

9. Custom Portal Profile (12th February 2024)​

Feature Requirement​

Add the Required fields in the My Profile Section of the Custom Portal.

Implementation​

We have currently added/modified the fields based on WIZ requirements.

Steps for checking the custom portal profile​

  1. Login to Custom Portal (https://wiz.cloudlabs.ai).

  2. On the right-hand side, you will be able to see the name xxxxxxxxx highlighted in the red.

  3. Click on the name you will be able to see the My Profile section.

  4. You will need to fill in the mandatory fields and click on Save Changes.

Lab User: Lab users will be unable to launch a lab or course if mandatory fields are not updated. Additionally, they should not be prompted for duplicate information in the registration form when attempting to launch a lab using an activation code in the custom portal.

Note: For any modifications on the above fields reach out to the Spektra team at Labs-support@spektrasystems.com

10. Spacing and Hyphens issue on the registration page (12th February 2024)​

Feature Requirement​

Need to allow the double spaces and the symbols (-) in the last name.

Implementation​

We are allowing the double spaces and symbols (-) in the last name.

Steps for checking the spacing and hyphens on the registration page​

  1. Allowing the hyphens in the Last Name.

  2. Allowing the Spaces in the Last Name.

11. Voucher Extension (12th February 2024)​

Feature Requirement​

Admin users must have the functionality to add 500 vouchers simultaneously.

Implementation​

We are allowing the admin user to add the 500 vouchers simultaneously.

Steps for checking the voucher extension​

  1. Go to On Demand Labs, choose the ODL you want to Add the vouchers for, and click on Edit (Highlighted in red below).

  2. Now you have a checkbox to choose for Enable voucher and click on submit.

  3. Navigate back to the same ODL, click on the ellipses option (...), and select Vouchers from the dropdown menu.

  4. Once the vouchers are selected, we will have an option to + Add Vouchers.

  5. Go to the count section and enter the number of vouchers required (As seen in the screenshot below)

Negative Testing: We are also trying to show the negative testing. If the “Count” increases to more than 500 you will not be able to add/submit the request.

Note: In such cases, need to contact the Spektra team to implement the required adjustments.

12. Inject and Static key Combination (12th February 2024)​

Feature Requirement​

The Inject Key should include both static and inject keys, with a copy option.

Implementation​

GitHub code snippet allows the usage of both static and inject keys simultaneously, with a copy option.

    <inject key="UserName" enableCopy="true" /> 

     **checkNNumber:** <inject key="UserName" value="StaticValue4" key="UserName" value="StaticValue4"  enableCopy="true" /> 

     **checkNNumber:** <inject key="AzureAdUserPassword" value="StaticValue2" key="AzureAdUserEmail" value="StaticValue1"  enableCopy="false" /> 

    **checkNNumber:** <inject key="AzureAdUserPassword" value="StaticValue3" key="UserName" value="StaticValue2" /> 

     **checkNNumber:** <inject key="UserName" value="StaticValue" key="UserName"  value="StaticValue" />    

     **url:** <inject key="AzureAdUserPassword" value="StaticValue2" key="AzureAdUserEmail" value="StaticValue1" enableCopy="false" />

Admin Portal: The below screenshot refers to the rendering of the inject and static key combination in the admin version.

Custom portal: The below screenshot refers to the rendering of the inject and static key combination custom portal.

13. Hide Feature in ODL for catalog view (12th February 2024)​

Feature Requirement​

Allow ODL or Lab to be visible for the specific domain.

Implementation​

Navigate to the On Demand lab, choose the Specific ODL, and click on the Edit option (as highlighted below).

Once we click on Edit look for the Enable Inside CL portal

In the Catalog State of Non-Allowed Domains, there are three options:

o Locked

o Unlocked

o Hidden

Steps for checking the hide feature in ODL for catalog view​

Example: For example, the specified domain is Gmail.

Locked​

Only the allowed domain will be able to launch the lab, we can check the other domains, but it will remain in lock state.

Positive testing: Login using the Gmail domain specified in the ODL is successful.

Negative testing: Login using the other domain is unsuccessful.

Unlocked​

All domains can use the launch option regardless of the specified allowed domain.

Hidden​

Set the Catalog State of Non-Allowed Domains to hidden, won't be able to view the ODL.

Positive testing: Login using the Gmail domain specified in the ODL is successful.

Negative testing: For Negative Testing, accessing the ODL won't be possible if logged in from the Spektra domain.

14. Custom Portal Catalog (21st March 2024)​

Feature Requirement​

Separate panel for the active labs with a resume button and a new tab for the retake count with a launch option.

Implementation​

On the custom portal's page under the “My Learning” section, you will be able to see the different panels for Active, Expired, Retake, and All labs.

Checking the custom portal catalog​

Active: Labs that are currently active will be displayed in the Active section, accompanied by a Resume button

Expired and Retakes: In this section, labs that are currently expired and which have a retake count left can be listed

All Labs: In this section, you can view the entire course list of users based on the Active/Expired and retake counts.

15. Addition of resources to the clean-up script. (22nd April 2024)​

Feature Requirement​

Implement the attendee resource clean-up for the below list.

  1. Reports
  2. Service Accounts
  3. Data Classifiers
  4. Automation Rule
  5. CICD Policy

Implementation:​

  1. Developed the API calls for the cleanup of the resources in the Wiz Portal.

16. GCP Sandbox. (22nd April 2024)​

Feature Requirement​

Set up the Sandbox feature on the Google Cloud Platform (GCP).

Implementation​

We're extending support for the GCP Sandbox feature within CloudLabs.

Steps to enable the GCP Sandbox.​

  1. Within the CloudLabs portal, navigate to the "On-Demand Lab" section, Locate the created On-Demand Lab (ODL), and click on the "Edit" option.

  2. Enable the Credit based allocation option inside the ODL.

  3. Once the credit-based allocation option is enabled, we need to Specify the Credit limit, add the Threshold limit for emails, and Action on Credit expiry.

    Credit Limit: Specify credits required to complete the Lab.

    Threshold limit for the Emails: CloudLabs will send an email notification to the user or instructor based on the usage specified in the ODL. For example, if the credit limit is set to $10 and the threshold email alert is set to 10%, the user or instructor will receive an alert when the usage reaches $1.

    Action on Credit Expiry: What action should be taken when credit expires.

    1. Auto_Deletion: Once the instance reaches the credit limit the instance will get deleted.

    2. Stop_All_Resources: If instances reache the credit limit, it will stop the resources.

    3. No_Action: Once the instances reache the credit limit, no action will be taken on any resources and instances.

  4. Once the Action on Credit Expiry scroll down to Click on submit to update the changes.

Note: Since cloud services provide precise cost details after 24 hours, we'll have the opportunity to receive alerts within a 24 to 48-hour window.

17. Inline Questions. (25th May 2024)​

The Inline Lab Guide Questions feature provides the ability to integrate an interactive Q&A module within Lab Guide.

The goal of this feature is to:

  1. Increase lab user engagement by introducing interactive elements in the lab guide.

  2. Assess the knowledge of the lab user by providing questions in the lab guide and grade the user based on question scores.

  3. Collection of valuable feedback from lab users to benefit both educators and CloudLabs.

  4. Ability to force users to answer questions in the current lab guide page to be able to move forward.

The feature supports two types of questions:

  • Single Choice

  • Multiple Choice

Configuring OnDemand Lab with Inline Lab Guide Questions:​

Step 1: Enable Inline Questions in Template config:

  • To enable Inline Questions, we need to input the master doc URL in the Template config, which will make the Render Inline Lab Guide Questions checkbox visible.

  • When the Render Inline Lab Guide Questions checkbox is selected, the feature flag will be enabled in the OnDemand Lab configuration.

Step 2: Enable Inline Questions in OnDemand lab config:

  • Once the Inline Questions feature has been enabled in the Template config, we need to input the master doc URL in the OnDemand lab config, which will make the Render Inline Lab Guide Questions checkbox visible.

  • When the Render Inline Lab Guide Questions checkbox is selected, inline questions will be displayed in the lab guide for new deployments.

FAQs:​

  1. How to enable Lab Guide questions for ongoing labs:

    To enable Inline questions for existing labs, we just need to update the lab guide and enable the ‘Render Inline Lab Guide Questions’ checkbox in the ODL config. It will a take few minutes to register the questions in CloudLabs. Once questions are registered, the changes will reflect for all the new deployments or retakes.

  2. How to update Lab Guide questions for ongoing labs:

    In case any Inline question has been updated (Added / Modified / Removed) in the lab guide, it will be synced automatically every 6 hours. To perform an on-demand sync, we can manually edit the ODL config and save it (no changes required in configuration), this will trigger an OnDemand sync of Inline questions.

Once the sync has been completed, changes done on the questions will reflect on existing OR new deployments based on the following rules:

  1. A new lab guide page is added – The questions on that will be available for new deployments/retakes only.

  2. A new question is added - it will be available for new deployments/retakes only.

  3. An existing question is removed - it will be removed for existing as well as new deployments/retakes.

  4. An existing question is updated, depending upon the change it will reflect for existing deployments:

    4.1. In case Question Type / Options / Answer is updated- changes will reflect for new deployments/retakes only.

    4.2. In Case Question Type, Options and Answer remain unchanged - The changes will reflect for existing deployments as well.

User Lab Experience:​

  • Once the feature has been enabled in the ODL config, attendees will be able to see inline questions like below:

  • To answer an Inline question, the user needs to select the appropriate option and click the Submit button.

  • It is possible to group multiple questions, in that case, a single Submit button will be visible to the user for all the questions in the group.

  • Once the answer has been submitted, the result will be shown instantly like below:

  • In case the user submits a wrong answer, a Retry button will be visible as below:

  • Retry option is available for a defined no of retries only which is configured in the lab guide.

Authoring Inline Lab Guide Questions:​

Below are the files that need to be created while authoring lab guide questions:

  1. Master Doc File -

  • This will be the parent file (JSON file) which is configured in the OnDemand Lab.

  • Master doc file contains the list of Lab guide page files and page unlocking rules.

    [
      {
        "Name": "How to Design a Lab Guide",
        "Language": "English",
        "Files": [
          {
            "RawFilePath": "https://docs-api-qa.cloudlabs.ai/repos/raw.githubusercontent.com/CloudLabs-AI/Practice-Test-Sample/main/qa-lab-guide/lab/01-single-question.md",
            "Order": 1
          },
          {
            "RawFilePath": "https://docs-api-qa.cloudlabs.ai/repos/raw.githubusercontent.com/CloudLabs-AI/Practice-Test-Sample/main/qa-lab-guide/lab/02-multiple-question.md",
            "Order": 2,
            "UnlockingRules": [
              {
                "UnlockDependency": "Questions",
                "DependentQuestions": [ "./questions/Page1/question-01.md", "./questions/Page1/question-02.md" ],
                "UnlockCriteria": "AnsweredCorrectly"
              }
            ]
          }
        ]
      }
    ]
  1. Lab Guide Page File –

  • The lab guide page file (markdown file) will contain the content to render on the lab guide page, along with inline question file tags.

  • To render inline questions in the lab guide page below tags can be used:

    For individual questions- For grouped questions- <grouped-questions source=”{relative question group file path}" />

    Please answer the following question
    <question source="../questions/Page7/question-01.md" />

    Please answer the following question
    <question source="../questions/Page7/question-02.md" />

    Please answer the following question
    <question source="../questions/Page7/question-03.md" />

    Please answer the following question
    <question source="../questions/Page7/question-04.md" />

    Please provide feedback about the lab guide
    <grouped-questions source="../questions/Page7/page-7-metadata.md" />

  1. Question Metadata File –

  • The question metadata file (markdown file) will contain the question-specific information required to render the question in the front end. It will also contain the correct answer and score for validation purposes and the number of allowed retries to submit the answer.

    ## Metadata
    Question Type : Single Choice

    ## Question
    What sensitivity labels are used by the military contractor to tag content?:

    ## Options
    Option 1: Top Secret, Secret, Unclassified

    Option 2: Confidential, Unclassified, Sensitive

    Option 3: Secret, Confidential, Unclassified

    Option 4: Private, Public, Unclassified

    ## Answers
    Option 3 : 1

    ## Correct Answer Feedback
    Option 3 is the correct answer

    ## Incorrect Answer Feedback
    Selected ## Option is not correct Option 3 is the correct answer

    ## Tags
    tag1
    tag2

    ## Number of Retries
    2
    ## Metadata
    Question Type : Multiple Choice

    Max Answers : 2


    ## Question
    Which severity level is assigned to the "Confidential Classification Rule" in the Wiz portal?:

    ## Options
    Option 1: Low

    Option 2: Medium

    Option 3: High

    Option 4: Critical

    ## Answers
    Option 2 : 1
    Option 3 : 1

    ## Correct Answer Feedback
    Option 2, 3 is correct answer

    ## Incorrect Answer Feedback
    Selected ## Options are not correct, Options 2, 3 is correct answer

    ## Tags
    tag1
    tag2

    ## Number of Retries
    5

  • Syntax of question metadata file:

    • Metadata -> Question Type:​

      It should be one of the below values-

      Single Choice (for single choice questions) OR Multiple Choice (for multiple choice questions)

    • Metadata -> Max Answers:​

      This field is used in case of multiple-choice questions to control the maximum number of options that can be selected by lab use on the front end. The value must be an integer having 2 as the minimum value OR the number of available options as the maximum value.

    • Question:​

      Content placed here will be visible as a question in the lab guide. A maximum of 4000 characters are allowed.

    • Options:​

      Content placed here (after :) will be visible as options in the lab guide.

      Content placed before the colon (:) is not visible to the lab user (It is used as an identifier for the given answers).

      Lab users can select one of more options and submit the answer.

    • Answers:​

      Content placed here will be used by CloudLabs to validate user answers and calculate user scores.

      In the case of a Single-Choice question, there can be only a single answer.

      In the case of Multiple-choice questions, there can be multiple answers (one answer in each row).

      The Value placed before the colon (:) is the identifier of the correct answer out of the given option.

      The Value placed after the colon (:) is the score.

    • Correct answer feedback:​

      Upon submission of the correct answer, this text will be shown to the lab user in the front end.

    • Incorrect answer feedback:​

      When the user submits an incorrect answer, this text will be shown to the lab user in the front end.

    • Tags:​

      This field is used as a tag and currently is not displayed anywhere. You can place any value here.

    • Number of Retries:​

      An integer value is used to control the number of allowed retries to submit the answer.

      To allow unlimited retries, set it to zero ‘0’. This field is not required in the case of grouped questions.

  1. Question Group File –

  • The question group file (markdown file) will contain the name of the question files that are part of the grouped question and the number of allowed retries to submit the answer.

  • Syntax of question group file:

    • Question:​

      Specify the question file names that are part of this grouped question.

    • Number of Retries:​

      An integer value is used to control the number of allowed retries to submit the answer.

      To allow unlimited retries, set it to zero ‘0’.

      ## Questions
      question-05
      question-06

      ## Number of Retries
      5

Page Unlocking Rules:​

Below page unlocking rules can be applied in the master doc:

  1. Answered - Ensures that the given list of questions has been answered by the user before proceeding further.

    "UnlockingRules": [
              {
                "UnlockDependency": "GroupedQuestions",
                "DependentQuestions": [ "./questions/Page7/page-7-metadata.md", "./questions/Page7/question-02.md" ],
                "UnlockCriteria": "Answered"
              }
            ]

  2. Answered Correctly - Ensures that the given list of questions has been answered correctly before proceeding further.

    "UnlockingRules": [
              {
                "UnlockDependency": "GroupedQuestions",
                "DependentQuestions": [ "./questions/Page5/question-05.md" ],
                "UnlockCriteria": "AnsweredCorrectly"
              }
            ]

  3. Score - Ensures that for the given list of questions, the user has received the required score before proceeding further.

    "UnlockingRules": [
              {
                "UnlockDependency": "GroupedQuestions",
                "DependentQuestions": [ "./questions/Page4/page-4-metadata.md" ],
                "UnlockCriteria": "Score",
                "UnlockPercentageThreshold": 50
              }
            ]

Example Scenarios:​

  1. Scenario 01:

    Single answer questions:

    Note: To ensure the questions are properly synchronized with the lab guide, create a dedicated folder for questions. This will make the questions well-organized and easily accessible.

    • Here is the question Markdown used in the Single Answer Question format:

      ## Metadata
      Question Type : Single Choice

      ## Question
      What sensitivity labels are used by the military contractor to tag content?:

      ## Options
      Option 1: Top Secret, Secret, Unclassified

      Option 2: Confidential, Unclassified, Sensitive

      Option 3: Secret, Confidential, Unclassified

      Option 4: Private, Public, Unclassified

      ## Answers
      Option 3 : 1

      ## Correct Answer Feedback
      Option 3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      2

    • Now, include the question Markdown file on the first page of the lab guide.

      Here is the inline question file tag used on the first page of the lab guide.

      Note: We can place question file tags wherever they're needed on the page, ensuring proper syntax is followed. Additionally, there's flexibility to include any number of questions.

      Note: We can include the full raw question Markdown file in both the lab guide and the master document.

    • To incorporate the unlocking rules for the first page, the question Markdown file should be included in the second order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as Answered. Therefore, even if the answer is incorrect, it should still allow progression to the next page. However, without attempting to answer it, progression to the next page will be blocked.

      Attendees will be able to see inline questions like below:

      Attendees can proceed to the next page by either answering the question correctly or incorrectly, based on the unlocking rules.

  2. Scenario 02:

    Multiple answers questions:

    • Here is the question Markdown used in the Multiple Answers Question format:

      ## Metadata
      Question Type : Multiple Choice

      Max Answers : 2


      ## Question
      Which severity level is assigned to the "Confidential Classification Rule" in the Wiz portal?:

      ## Options
      Option 1: Low

      Option 2: Medium

      Option 3: High

      Option 4: Critical

      ## Answers
      Option 2 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Option 2, 3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options are not correct, Option 2, 3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5

    • Now, include the question Markdown files on the second page of the lab guide.

      Here is the inline question file tag used on the second page of the lab guide.

    • To include the unlocking rules for the second page, the question Markdown file should be included in the third order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as AnsweredCorrectly. Therefore, the answer should be correct to proceed to the next page.

      Attendees will be able to see inline questions like below:

      Attendees can proceed to the next page by answering the question correctly, based on the unlocking rules.

  3. Scenario 03:

    Single and Multiple answers questions:

    • Here is the question Markdown used in the Single and Multiple Answers Question format:

      ## Metadata
      Question Type : Single Choice

      ## Question
      Which of the following steps is NOT part of creating a data classification rule in the Wiz portal?:

      ## Options
      Option 1: Selecting the data type

      Option 2: Defining the severity level

      Option 3: Setting the maximum unique matches

      Option 4: Uploading the file to be classified

      ## Answers
      Option 4 : 1

      ## Correct Answer Feedback
      Option 4 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options are not correct Option 4 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      4
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 3

      ## Question
      What is the purpose of setting the "Minimum unique matches" field when creating a data classification rule in the Wiz portal?:

      ## Options
      Option 1: To determine the number of files to be scanned

      Option 2: To specify the minimum number of occurrences of the classified data within a single file

      Option 3: To control the sensitivity level of the classification rule

      Option 4: To prioritize the scanning of certain file types

      ## Answers
      Option 2 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Option 2, 3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2, 3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      4

    • Now, include the question Markdown file on the Third page of the lab guide.

      Here are the inline questions file tags used on the Third page of the lab guide.

    • To include the unlocking rules for the Third page, the question Markdown file should be included in the fourth order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as AnsweredCorrectly. Therefore, the answer should be correct to proceed to the next page.

      Attendees will be able to see inline questions like below:

      Attendees can proceed to the next page by answering the question correctly, based on the unlocking rules.

  4. Scenario 04:

    Grouped single answer questions:

    • Here are the question Markdowns used in the Grouped single answer questions format: 

      ## Metadata
      Question Type : Single Choice

      ## Question
      What is the purpose of setting the "Minimum unique matches" field when creating a data classification rule in the Wiz portal?:

      ## Options
      Option 1: To determine the number of files to be scanned

      Option 2: To specify the minimum number of occurrences of the classified data within a single file

      Option 3: To control the sensitivity level of the classification rule

      Option 4: To prioritize the scanning of certain file types

      ## Answers
      Option 2 : 1

      ## Correct Answer Feedback
      Option 2 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Option is not correct, Option 2 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Single Choice

      ## Question
      Which of the following steps is NOT part of creating a data classification rule in the Wiz portal?:

      ## Options
      Option 1: Selecting the data type

      Option 2: Defining the severity level

      Option 3: Setting the maximum unique matches

      Option 4: Uploading the file to be classified

      ## Answers
      Option 4 : 1

      ## Correct Answer Feedback
      Option 4 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Option is not correct, Option 4 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5

    • Now, include the question Markdown file on the fourth page of the lab guide.

      Here is the inline question file tag used on the fourth page of the lab guide.

      Note: As these are grouped questions, we need to have a grouped Markdown file (metadata file) in the same group where the actual questions related to this metadata are located.

    • To include the unlocking rules for the fourth page, the question Markdown file should be included in the fifth order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as Score. Therefore, the answer should be based on the score, and one should meet the threshold. Since there are two questions, the combined score should meet the 50% threshold to proceed to the next page.

      Attendees will be able to see inline questions like below:

      The score will not be displayed as of now, but based on two questions and a 50% threshold, if at least one is answered correctly, it will allow progression to the next page.

  5. Scenario 05:

    Grouped Multiple answers questions:

    • Here are the question Markdowns used for the Grouped Multiple Answers Questions format: 

      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      In the context of GitHub, what does the term "fork" mean?:

      ## Options
      Option 1: To create a duplicate of a repository under your GitHub account

      Option 2: To merge changes from one branch into another

      Option 3: To create a new branch from an existing one

      Option 4: To revert changes made in a commit

      ## Answers
      Option 1 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Options 1, 3 are the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options are not correct, Options 1, 3 are the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      What is the purpose of a pull request in GitHub?:

      ## Options
      Option 1: To request changes to a repository

      Option 2: To review changes made in a branch before merging them into another branch

      Option 3: To undo changes made in a commit

      Option 4: To create a new branch from an existing one

      ## Answers
      Option 1 : 1
      Option 2 : 1

      ## Correct Answer Feedback
      Option 1, 2 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options are not correct, Options 1, 2 are the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5

    • Now, include the question Markdown file on the fifth page of the lab guide.

      Here is the inline question file tag used on the fifth page of the lab guide.

      Note: As these are grouped questions, we need to have a grouped Markdown file (metadata file) in the same group where the actual questions related to this metadata are located.

    • To include the unlocking rules for the fifth page, the question Markdown file should be included in the sixth order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as AnsweredCorrectly. Therefore, the answer should be correct to proceed to the next page.

      Attendees will be able to see inline questions like below:

      Attendees can proceed to the next page by answering the question correctly, based on the unlocking rules.

  6. Scenario 06:

    Grouped Single and Multiple answers questions:

    • Here are the question Markdowns used for the Grouped Single and Multiple Answers Questions format:

      ## Metadata
      Question Type : Single Choice

      ## Question
      What is the purpose of creating a new branch when committing changes to a GitHub repository?:

      ## Options
      Option 1: To separate different versions of the code

      Option 2: To merge changes from one branch into another

      Option 3: To revert changes made in a commit

      Option 4: To create a duplicate of a repository under your GitHub account

      ## Answers
      Option 2 : 1

      ## Correct Answer Feedback
      Option 2 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Single Choice

      ## Question
      What does the "Wiz IaC Scanner" check for during the CI/CD process?:

      ## Options
      Option 1: Code syntax errors

      Option 2: Infrastructure as Code misconfigurations

      Option 3: Vulnerabilities in the code

      Option 4: Secret keys stored in the code

      ## Answers
      Option 2 : 1

      ## Correct Answer Feedback
      Option 2 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      What action is recommended when the "Wiz Secret Scanner" fails during a pull request check?:

      ## Options
      Option 1: Ignore the findings and proceed with merging

      Option 2: Address the identified secrets in the code

      Option 3: Submit the pull request without addressing the issues

      Option 4: Revert the changes made in the pull request

      Option 5: Ignore the findings

      ## Answers
      Option 2 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Option 2,3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2,3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      2
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      Why is it important to address the issues found by the Wiz scanners during the CI/CD process?:

      ## Options
      Option 1: To increase the number of commits in the repository

      Option 2: To enhance the code quality and security

      Option 3: To speed up the deployment process

      Option 4: To create more branches in the repository

      Option 5: To only increase the number of commits

      ## Answers
      Option 2 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Option 2,3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2,3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      2

    • Now, include the question Markdown file on the sixth page of the lab guide.

      Here is the inline question file tag used on the sixth page of the lab guide.

      Note: As these are grouped questions, we need to have a grouped Markdown file (metadata file) in the same group where the actual questions related to this metadata are located.

    • To include the unlocking rules for the sixth page, the question Markdown file should be included in the seventh order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as Answered. Therefore, even if the answer is incorrect, it should still allow progression to the next page. However, without attempting to answer it, progression to the next page will be blocked.

      Attendee will be able to see inline questions like below:

      Attendees can proceed to the next page by either answering the question correctly or incorrectly, based on the unlocking rules.

  7. Scenario 07:

    Single and Multiple answers questions:

    Grouped Single and Multiple answers questions:

    • Here are the question Markdowns used for Single and Multiple Answers question format, as well as for Grouped Single and Multiple Answers question format:

      ## Metadata
      Question Type : Single Choice

      ## Question
      What is the purpose of the "Wiz IaC Scanner" in the CI/CD pipeline?:

      ## Options
      Option 1: To check for vulnerabilities in the code

      Option 2: To review changes made in a branch before merging them into another branch

      Option 3: To scan for Infrastructure as Code misconfigurations

      Option 4:  To revert changes made in a commit

      ## Answers
      Option 3 : 1

      ## Correct Answer Feedback
      Option 3 is the correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 3 is the correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      2
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      What action did the author take in response to the "Wiz IaC Scanner" finding regarding the Dockerfile?:

      ## Options
      Option 1: Ignored the finding and proceeded with merging

      Option 2: Addressed the misconfiguration in the Dockerfile

      Option 3: Reverted the changes made in the commit

      Option 4: Created a new branch to isolate the issue

      Option 5: Ignored the finding 


      ## Answers
      Option 1 : 1
      Option 2 : 1

      ## Correct Answer Feedback
      Option 1, 2 is correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 1, 2 is correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Single Choice

      ## Question
      What is the potential consequence of ignoring the findings from the "Wiz Secret Scanner"?:

      ## Options
      Option 1 : Increased code quality and security

      Option 2 : Reduced risk of compromise and privilege escalation

      Option 3 : Enhanced integration with the CI/CD pipeline

      Option 4 : Higher likelihood of exposing sensitive credentials

      ## Answers
      Option 4 : 1

      ## Correct Answer Feedback
      Option 4 is correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 4 is correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      5
      ## Metadata
      Question Type : Multiple Choice
      Max Answers : 2

      ## Question
      Why did the author choose to merge the pull request despite the "Wiz Secret Scanner" finding?:

      ## Options
      Option 1: To increase the number of commits in the repository

      Option 2: To speed up the deployment process

      Option 3: To demonstrate bypassing checks in the CI/CD pipeline

      Option 4: To address all findings before merging

      ## Answers
      Option 2 : 1
      Option 3 : 1

      ## Correct Answer Feedback
      Option 2, 3 is correct answer

      ## Incorrect Answer Feedback
      Selected ## Options is not correct Option 2, 3 is correct answer

      ## Tags
      tag1
      tag2

      ## Number of Retries
      2

    • Now, include the question Markdown file on the seventh page of the lab guide.

      Here is the inline question file tag used on the seventh page of the lab guide.

      Note: As these are grouped questions, we need to have a grouped Markdown file (metadata file) in the same group where the actual questions related to this metadata are located.

    • To include the unlocking rules for the seventh page, the question Markdown file should be included in the eighth order of the raw file path within the Master Doc file.

      Here are the unlocking rules for this question: It is marked as Answered. Therefore, even if the answer is incorrect, it should still allow progression to the next page. However, without attempting to answer it, progression to the next page will be blocked.

      Attendees will be able to see inline questions like below:

      Attendees can proceed to the next page by either answering the question correctly or incorrectly, based on the unlocking rules.

18. Adding a ReadOnly Access Permission to the AWS Template (2nd July 2024)​

Overview​

CloudLabs Template is the base of the hands-on lab environment. You can do a variety of configurations under Templates, such as adding prerequisites, enabling ReadOnly Access Permission, custom policies for users, and much more.

Here we will learn more about how to add ReadOnly Access Permission using the CloudLabs Template.

Prerequisites​

Before you begin adding ReadOnly Access permission, ensure you have the following prerequisites:

  1. Admin access to CloudLabs Admin Portal (If access is unavailable, kindly reach out to your point of contact or CloudLabs Support).

Add a ReadOnly Access Permission to the Template​

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Navigate to the Templates (1) section in the left menu (1), select an existing template (2), and click the Edit button (3) in the Template section.

  3. Then scroll down to the Template Permissions section and click on the Add button.

  4. Under Permission type, select IAM Built-in Policy from the drop-down.

  5. Under Profile type, select Attendee from the drop-down.

  6. Under Permission, select ReadOnly Access from the drop-down.

  7. Then click on the Submit button.

  8. After submitting the Template permissions, click the Submit button for the template.

Setup Template on CloudLabs​

Follow the below-mentioned guide to set up a new AWS Template on CloudLabs.

19. Manage Permissions through Control Panel(AWS) - (12 July 2024)​

Feature requirement:​

Manage AWS permissions for all the Attendees through the Control Panel.

Implementation:​

Enabled the feature that will allow us to manage the AWS permissions from the Control Panel.

Steps for managing permissions from the Control Panel:​

  1. Navigate to the On Demand Labs (1) page on the Cloud Labs Admin portal, select the On Demand Lab that you have created, and click on the Control Panel (2) button under the Actions.

  2. On the Control Panel page, scroll down and click on the Manage Permissions options under the Others.

  3. On the Permissions page, verify the Status of the permission like Applied, Removed, or Not Applied.

  4. If you want to Apply the permission to all the Attendees then click on the Apply button under the Actions tab.

Note: This action will apply permission to all the current active deployments present in the On-Demand Lab.

  1. Click on OK on the pop-up "This action will apply current permission to ALL attendees in the ODL. Are you sure you want to proceed?" if you want to Apply the permission to all the Attendees present in the On Demand Lab.

  2. Verify that permission status is Applied under the Status tab.

Note: If the changes are not reflected automatically, click on the Refresh button to verify the latest changes.

  1. If you want to Remove the permission from all the attendees, click on the Remove button under the Actions tab.

Note: This action will remove the permission from all the currently active deployments present in the On Demand Lab.

  1. Click OK on the pop-up that says, This action will remove current permissions from ALL attendees in the ODL. Are you sure you want to proceed? if you want to Remove the permission from all the attendees present in the On Demand Lab.

  2. Verify that the permission status is Removed under the Status tab.

Note: If the changes are not reflected automatically, click on the Refresh button to verify the latest changes.

20. Adding Organization Account Access Role for Instructor(AWS) - (12 July 2024)​

Feature Requirement:​

Add an organization Account access role to instructor user profile.

Implementation:​

Enabled template permission which will allow you to add the organization Account access role to instructor user profile.

Steps to Add an organization Account access role to the instructor user profile.​

Assign permission to the instructor.​

  1. Navigate to the Templates on the CloudLabs admin portal from the left-hand panel.

  2. Click on Edit for the template where you want to assign the Organization Account Access role to the Instructor.

  3. Navigate to the Template Permission section and click on +ADD.

  4. Choose the configurations as specified below, then click Submit:

    • Permission Type: IAM Instructor Access

    • Profile Type: Instructor

    • Permission: Organization Account Access Role

Add the Instructor at the ODL level:​

  1. In the On Demand Lab section, choose the ODL (On Demand Lab) where you wish to add the instructor, then click on the icon indicated in the image below:

  2. Select the Manage Instructors.

  3. In the Manage Instructor section, click on +ADD INSTRUCTOR.

  4. In the ADD INSTRUCTOR section, enter the First Name, Last Name, Email, and Organization of the Instructor, then click SUBMIT.

  5. On the Manage Instructor page, once the instructor is created to obtain the cloud credentials, click on the symbol indicated in the image below in the Actions section.

  6. In the Instructor Cloud details popup, click on Create Cloud User.

  7. Once you click on Create Cloud User you can obtain the cloud credentials for the instructor in the Instructor Cloud Details section.

Note: Using the above credentials, instructors can switch to user accounts through the Organization Account Access Role.

Switch to the User Account with Instructor credentials.​

  1. Log in to the admin portal using the instructor credentials.

  2. In the On Demand Lab section, click on the user icon for the assigned On Demand Lab (ODL).

  3. Click on Lab Details for the succeeded instance in the user's section under Actions and Copy the Account ID of the User.

  4. Sign in to the AWS Console using the credentials provided when adding the instructor to the On Demand Lab (ODL).

  5. Once logged into the instructor environment, if the instructor needs to access the users' environment, click on Switch role.

  6. In the Switch role section, enter the Account ID of the user that you copied in the previous step. For the IAM Role Name, enter OrganizationAccountAccessRole and click on Switch role to switch to the user's environment.

21. GCP Custom Role - (15 August 2024)​

Feature Requirement​

GCP Custom Role for tailoring access to meet the specific needs.

Implementation​

The GCP custom role in JSON format can be loaded into a template and that can be effectively applied onto the users.

Steps for Implementing GCP Custom Role​

  1. Create a GCP Custom Role in JSON Format. The example below is a GCP role that grants tailored permissions to the Big Query service.
{
  "role": {
      "title": "bigquerydemo",
      "includedPermissions": [
        "bigquery.datasets.get",
        "bigquery.datasets.getIamPolicy",
        "bigquery.models.export",
        "bigquery.models.getData",
        "bigquery.models.getMetadata",
        "bigquery.models.list",
        "bigquery.routines.get",
        "bigquery.routines.list",
        "bigquery.tables.createSnapshot",
        "bigquery.tables.export",
        "bigquery.tables.get",
        "bigquery.tables.getData",
        "bigquery.tables.getIamPolicy",
        "bigquery.tables.list",
        "bigquery.tables.replicateData",
        "resourcemanager.projects.get",
        "resourcemanager.projects.list"
      ],
      "description": "bigquery role"
  },
  "roleId": "bigqueryroletest"
}

Note : In the above given Role,

  • title is the name given to a Role for easy identification on the GCP Console.
  • includedPermissions is a set of permissions that are granted to a user. More permissions can be added or removed for a customized Role. A Role can have permissions for different services or for a single service.
  • description, is used to describe the function of the Role.
  • roleId is a unique identifier for the custom role.
  1. Store the JSON Role file in a Google Cloud Storage Bucket or AWS S3 bucket and copy the URL of the file.

Note : The stored file in the bucket should be accessible.

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Click on Edit for the template where you want to upload the Custom role.

  3. Navigate to the IAM section and click on +ADD.

  4. Choose the configurations as specified below, then click Submit:

  • Role Type: Custom Role

  • Profile Type: Attendee

  • Custom Role URL: Paste the copied URL of the Custom Role here

  1. Now, navigate to On Demand Labs section and click on users for the ODL associated with the GCP Role Template.

  2. Click on Add User, fill out the user details, and launch the environment.

  3. Copy the GCP Console link and login credentials as shown below.

  4. Login to the GCP Console by entering the copied Username and Password.

  5. On the GCP Console, under the Admin Project, type Roles in the search bar and navigate to that Section.

Note : The GCP user should have permission to view the IAM and Admin Console to follow Step 13 and 14.

  1. Search for the title bigquerydemo in the filter section. The Custom Role that was applied from CL can be found in the Roles section. Since the title given in the JSON custom Role was bigquerydemo, the Role will be saved under the same name.

  2. On the GCP Console, click on the search bar to find the Big Query Service.

  3. On the BigQuery Console, we can examine the effectiveness of the BigQuery Custom Role we created in step 1.

Note : As shown in the above picture, the BigQuery Role has been successfully applied to the user. Therefore, the user can perform actions that are mentioned inside the Role.

22. Inline Question Fixes - (15 August 2024)​

Feature Requirement​

The feedback color for all the Grouped questions was influenced by the outcome of the first question and If the question is correct still the answer was highlighted in red.

Implementation​

Issue resolved by assigning appropriate colors to the feedback: green for correct answers and red for incorrect answers.

Issues and their Resolutions​

1. Issue 1​

The feedback color for all questions was influenced by the outcome of the first question. If the first question was answered incorrectly, the feedback for subsequent questions was displayed in red, regardless of the correctness of their answers.

Fixes for Issue 1​

If the answer to the first question is incorrect, the feedback will be in red; for subsequent questions, the feedback color will depend on the correctness of each answer.

2. Issue 2​

Even when the correct answer was provided, it was still highlighted in red.

Fixes for Issue 2​

If the answer to the question is correct, the feedback will be in green.

23. Terraform Implementation - (15 August 2024)​

Requirement​

Enabling Terraform template support in CloudLabs.

Implementation​

This feature allows a user to deploy the resources using a Terraform engine.

Steps to set up a Terraform template​

  • Note : Please ensure that the flag Enable Terraform: true at the system admin level should be enabled for the Terraform feature to work.

  1. Login to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Click on Edit for the template where you want to upload the Terraform template.

  3. Click on the Add button under the “Deployment Manager Template” section if the Cloud Platform is GCP.

Note

  • If the Cloud Platform is AWS, the section will be named as CloudFormation Template.

  • If the Cloud Platform is Azure, the section will be named as ARM Template

  1. Choose the configurations as specified below, then click Submit:

  • Template Type: Terraform

  • Template File Type: TF or JSON

  • Custom Role URL: Paste the URL of the terraform file either in tf or json format.

  1. Now, navigate to On Demand Labs section. Create an ODL using this template and click on users for this newly created ODL.

Note : To learn how to create an ODL, click here

  1. Click on Add User, fill out the user details, and launch the environment.

  2. Once the deployment is complete, status can be seen under the Deployment Activity Log in the lab status section.

Success Scenario:​

Failure Scenario:​

Limitations​

  • Terraform template can’t be added to a shared subscription (Reason: Terraform can create additional RGs which will be left during cleanup).
  • RDP over HTTPS feature is not supported at this moment (Added to the next iteration).

References​

Sample TF files:​

Sample JSON files:​

24. Auto Extension Approval - (15 August 2024)​

Feature Requirement​

This feature was needed to streamline the process of extending duration and credit under managerial oversight.

Implementation​

The solution involves configuring settings at the ODL level to enable duration and credit extensions with manager approval.

Steps for Enabling Manager-Approved Duration and Credit Extension Feature​

  1. Log in to the CL portal and click on + ADD ON DEMAND LAB in the On Demand Labs section.

  2. Name the ODL, choose a template to associate with it, and complete all the required details.

  1. To add the Duration Extension feature to your ODL, ensure that you click on the checkbox labeled "Allow user to Extend lab" and select the configurations as specified below."

  • Max Limit of Duration Extension by User : Specifies the maximum time duration.

  • Allowed Extend Duration By Attendee : Specifies the time interval for extensions within the max limit.

  • Disable Duration Auto Approval : Ensure to click on this checkbox for manager approval.

  1. To add the Credit Extension feature to your ODL, ensure that you click on the checkbox labeled "Allow user to Extend Credit" and select the configurations as specified below."

  • Max Credit Limit : Specifies the maximum Credit extension limit.

  • Allowed Credit Limit : Specifies the credit interval for extensions within the max limit.

  • Disable credit Auto Approval : Ensure to click on this checkbox for manager approval.

  1. Click on the Submit Button after enabling the Duration and Credit Extension Feature.

Steps for Testing Manager-Approved Duration and Credit Extension Feature​

  1. Navigate to the On Demand Labs section and click on Users for the ODL where the Duration Extension and Credit Extension features have been enabled.

  2. Click on Add User, fill out the user details, and launch the environment.

  3. On the top right corner of the page, click on the duration extension icon as shown below.

  4. Click on Okay to extend the duration of the lab.

  5. The requester will receive an email confirming the duration Extension.

  6. On the top right corner of the page, click on the Credit extension icon as shown below.

  7. Click on Okay to extend or increase the credit.

  8. The requester will receive an email confirming the Credit Extension.

Manager's Approval Process for Duration or Credit Extensions​

  1. The manager will receive an email as soon as a duration or credit extension is requested by the requester.

Note : The above image represents the email for credit extension.

  1. Once the manager approves the request, the duration or credit extension will automatically take effect in the ongoing lab.

Note : The above image represents credit extension approval.

25. Personal Email Consideration in Tenant Level - (30 September 2024)​

Feature Requirement​

Need to add the me.com and icloud.com for the Personal Email address.

Implementation​

me.com and icloud.com are considered as the Personal Email address.

Allowing Personal email consideration​

If we are allowing the personal Email address at the ODL level then Users can able to register with me.com and icloud.com.

Steps for enabling, Disabling and Checking the functionalities of allowing personal email address.​

  1. Log in to the Cloud Labs portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the ODL section.

  2. Navigate to the necessary ODL and select the edit (1) button.

  3. Then navigate down and select the checkbox labeled Allow personal email addresses.

  4. Click on the Submit button.

Testing scenario:​

  1. Allow personal email addresses enabled:

  2. Allow personal email addresses disabled:

26. Retake Count Should Not Consider for Failed Deployments - (30 September 2024)​

Feature requirement​

Prevent retake count from decrementing when a deployment fails due to an error.

Implementation​

When an instance or environment is deployed and fails, the retake count for failed deployments will not decrease. For each successful deployment, the retake count decreases by 1. For example, if the retake count is initially set to 5 and the deployment fails due to a template error, the count remains at 5.

Validating the retake count functionality​

Phase 1: Testing the retake count for successful deployments.​

  1. Initially, the retake Count is set to 15 (1) before launching the environment, as shown below.

  2. The Instance is launched by clicking the “Relaunch (1)” button as shown below.

  3. The deployment of the environment will succeed.

  4. The retake count gets reduced by 1 as a successful deployment has taken place. The No. of attempts or the retake count getting reduced is expected for successful deployments.

Phase 2: Testing the retake count for failed deployments.​

  1. Let the initial retake Count be 14 before launching the environment, as shown in the image below.

  2. To test the retake count, the CloudLabs template is modified to obtain failed deployments.

  3. The Instance is relaunched by clicking the “Relaunch (1)” button as shown in the picture.

  4. The deployment of the environment will fail.

  5. The retake count remains the same as it was before deployment. The number of attempts, or the retake count, is expected to stay unchanged for failed deployments according to the requirements and implementation.

27. AWS Forecasted Costs in CloudLabs - (30 September 2024)​

Feature Requirement​

This feature allows users to view AWS forecasted costs directly within the CloudLabs platform, providing real-time insights into their budget and usage.

Implementation​

Integrate AWS forecasting into CloudLabs, allowing users to view forecasted costs directly in the control panel.

Steps for checking AWS forecasted cost​

  1. Log in to the CL portal, navigate to the Templates (1) section, and click on "+ ADD (2)" to create a new template.

  2. Name the template (1), select AWS as the Cloud Platform (2), and fill in all the required details. Note : To learn how to create a template, click here

  3. To deploy resources for cost forecasting, the user can either specify CloudFormation templates and parameter files or create the resources directly in the AWS console. To create resources using a CFT, provide the URL of the CFT and the parameter file as shown below in the template section and click on Submit.

  4. To create resources on the AWS console or to list or describe them, provide the necessary template permissions based on the requirements and click on Submit.

  5. Navigate to the On Demand Labs (1) section and click + ADD ON-DEMAND LAB (2) in the top-right corner to create a new ODL.

  6. Name the ODL(1), choose the newly created template(2) to associate with it, and fill in all the required details.

    Note : To learn how to create an ODL, click here

  7. Additionally, click on "Enable Credit-Based Allocation" while creating the ODL to retrieve the forecasted costs, and then Submit.

  8. In the On Demand Labs (1) section, click on Users (2) for the ODL associated with Cost Forecasting.

  9. Click on Add User, fill out the user details, and launch the environment.

  10. Log in to the AWS account using the provided credentials and deploy the resources. If the resources are deployed via the CFT, ensure that all the resources have been created successfully.

  11. In the CloudLabs On Demand Labs (1) section, click on Control Panel (2) for the ODL associated with Cost Forecasting to monitor the forecasted costs.

  12. Under the Control Panel (1), click on "Cloud Cost (2)".

  13. The forecasted cost for the current ongoing lab will be displayed under the "Forecasted Cost(1)" section. If any new deployments occur, the forecasted costs will be updated accordingly.

28. GCP Forecasted Costs in CloudLabs - (30 September 2024)​

Feature Requirement​

This feature allows users to view GCP forecasted costs directly within the CloudLabs platform, providing real-time insights into their budget and usage.

Implementation​

Integrate GCP forecasting into CloudLabs, allowing users to view forecasted costs directly in the control panel.

Steps for checking GCP forecasted cost​

  1. Log in to the CL portal, navigate to the Templates (1) section, and click on "+ ADD (2)" to create a new template.

  2. Name the template (1), select GCP as the Cloud Platform (2), and fill in all the required details.

  • Note : To learn how to create a template, click here

  1. To deploy resources for cost forecasting, the user can either specify the Deployment Manager template or create the resources directly in the GCP console.

  • To create resources using a Deployment Manager template, provide the URL of the template as shown below and click on Submit.

  1. To create resources on the GCP console or to list them, provide the necessary permissions under IAM based on the requirements and click on Submit.

  2. Navigate to the On Demand Labs (1) section and click + ADD ON-DEMAND LAB (2) in the top-right corner to create a new ODL.

  3. Name the ODL (1), choose the newly created template(2) to associate with it, and fill in all the required details.

  1. Additionally, click on "Enable Credit-Based Allocation" while creating the ODL to retrieve the forecasted costs, and then Submit.

  2. In the On Demand Labs (1) section, click on Users (2) for the ODL associated with Cost Forecasting.

  3. Click on Add User, fill out the user details, and launch the environment.

  4. Log in to the GCP console using the provided credentials and deploy the resources. If the resources are deployed via the Deployment Manager Template, ensure that all the resources have been created successfully.

  5. In the CloudLabs On Demand Labs (1) section, click on Control Panel (2) for the ODL associated with Cost Forecasting to monitor the forecasted costs.

  6. Under the Control Panel (1), click on "Cloud Cost (2)".

  7. The forecasted cost for the current ongoing lab will be displayed under the "Forecasted Cost (1)" section. If any new deployments occur, the forecasted costs will be updated accordingly.

29. OCI Phase 2 - (30 September 2024)​

Multi-Region Deployment using OCI​

Overview​

Users can now deploy OCI resources in multiple regions. Currently, it is limited to us-ashburn-1, uk-london-1, and ap-hyderabad-1.

Prerequisites​

  • Before adding multiple regions to the template, ensure you have the following prerequisites:

    Admin access to CloudLabs Admin Portal (If access is unavailable, kindly reach out to your point of contact or CloudLabs Support).

Adding Multiple Region​

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Navigate to the Templates (1) section in the left menu and click on the edit (2) button.

  3. Scroll down to the Region (1) section and choose the regions. Then click on the Submit (2) button.

  4. Navigate to the ODL (1) section in the left menu and click on the edit (2) button.

  5. After clicking on the edit button, choose the same regions that were updated at the template level.

  6. Then scroll down and click on the Submit button.

Testing scenario:​

Once the users are deployed, below are the outputs for all the regions with resources deployed in each region.

  • us-ashburn-1

  • uk-london-1

  • ap-hyderabad-1

Hot Instance in OCI​

Overview​

Hot instances can now be added using OCI as the cloud platform.

Prerequisites​

  • Before adding hot Instances to the ODL, ensure you have the following prerequisite:

    Admin access to CloudLabs Admin Portal (If access is unavailable, kindly reach out to your point of contact or CloudLabs Support).

Adding Hot Instances​

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Navigate to the ODL (1) section in the left menu and click on the edit (2) button.

  3. Scroll down to the Enable Hot Instances section and enable the checkbox.

  4. Then click on the Submit button.

  5. Once the ODL is submitted, click on the Hot Instance button.

  6. Next, click on the + ADD button (1) and provide the Number of Hot Instances (2) needed. Then click on the Add (3) button.

  7. Once the hot instances are added, below is the output for all the regions.

OCI Resource Usage Policy​

Overview​

OCI Resource Usage Policy is used to monitor the cores and clusters of OCI resources that are predefined for a user.

Prerequisites​

Before adding the OCI Resource Usage Policy in the Template, ensure you have the following prerequisites:

Adding OCI Resource Usage Policy​

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, you will see the Template section.

  2. Navigate to the Templates (1) section in the left menu and click on the edit (2) button.

  3. Scroll down to the Usage Policy section and provide the Usage Policy URL for the respective OCI resource.

    ![](/img/wiz/ociusage /02.png)

  4. Then, click the Submit button.

Usage Policy and Alerts Outputs​

Below are the Resource Usage Policy and Alerts outputs for the respective resources.

  1. Instance :

    i. The metric used is count of instances.

    • Policy:

      [
        {
          "ResourceType": "OCI.Instance",

          "Parameter": [
            {
              "Name": "max-ocpu-cores",

              "Value": "1"
            },

            {
              "Name": "max-memory-gb",

              "Value": "32"
            },

            {
              "Name": "max-instance-count",

              "Value": "1"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

      Alert:

    ii. The metrics used include OCPU Cores and Memory (GB).

    • Output:

      In the OCI Console:

      Alerts:

  2. Bucket : The metric used is Storage (GB).

    • Policy:

      [
        {
        "ResourceType": "OCI.Bucket",
        "Parameter": [
            {
            "Name": "max-storage-gb",
            "Value": "1"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

  3. Boot Volume : The metrics used include VPUs (per GB) and Volume (GB).

    • Policy:

      [
        {
          "ResourceType": "OCI.BootVolume",
          "Parameter": [
            {
              "Name": "max-volume-gb",
              "Value": "50"
            },
            {
              "Name": "max-vpus",
              "Value": "10"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

      Alert:

  4. Block Volume : The metrics used include VPUs (per GB) and Volume (GB).

    • Policy:

      [
        {
          "ResourceType": "OCI.Volume",

          "Parameter": [
            {
              "Name": "max-volume-gb",

              "Value": "50"
            },

            {
              "Name": "max-vpus",

              "Value": "10"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

      Alert:

  5. Boot Volume Backup : The metric used is Volume (GB).

    • Policy:

      [
        {
          "ResourceType": "OCI.BootVolumeBackup",
          "Parameter": [
            {
              "Name": "max-volume-gb",
              "Value": "4"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

      Alert:

  6. Block Volume Backup : The metric used is Volume (GB).

    • Policy:

      [
        {
          "ResourceType": "OCI.VolumeBackup",

          "Parameter": [
            {
              "Name": "max-volume-gb",

              "Value": "6"
            }
          ]
        }
      ]

    • Output:

      In the OCI Console:

  7. File System : The metric used is Storage (GB).

    • Policy

      [
        {
           "ResourceType": "OCI.FileSystem",
           "Parameter": [
             {
               "Name": "max-storage-gb",
               "Value": "1"
              }
             ]
          }
       ]

    • Output In the OCI Console:

      Alert:

  8. PostgreSQL DB System : The metrics used include max-ocpu-cores, max-memory-gb, max-nodes, and max-iops.

    • Policy

      [
          {
            "ResourceType": "OCI.PostgreSqlDbsystem",
             "Parameter": [
               {
                   "Name": "max-memory-gb",
                   "Value": "30"
               },
               {
                   "Name": "max-nodes",
                   "Value": "1"
               },
              {
                   "Name": "max-iops",
                   "Value": "70000"
               }
             ]
          }
      ]

    • Output

      Alert:

  1. DB System : The metrics used include max-nodes, max-cluster-memory-gb, max-storage-gb, max-memory-gb, and max-cpu-cores.

    i. The metric used is

  • Policy

    [
        {
           "ResourceType": "OCI.DbSystem",
            "Parameter": [
               {
                   "Name": "max-cpu-cores",
                   "Value": "1"
               },
               {
                   "Name": "max-memory-gb",
                   "Value": "16"
               },
               {
                   "Name": "max-storage-gb",
                   "Value": "1024"
               },
               {
                   "Name": "max-cluster-memory-gb",
                   "Value": "32"
               },
               {
                   "Name": "max-nodes",
                   "Value": "1"
               }
            ]
        }
    ]

  • Output

    Alert:

Below is the usage policy URL for all OCI resources, including Volume Backup, Boot Volume Backup, Boot Volume, Functions, DB System, Autonomous Database, PostgreSQL DB System, File System, Volume, Bucket, and Instance.

30. Extension of Duration Based on Hours and Days - (19 November 2024)​

Overview​

Attendees will be able to extend the duration of their lab in increments of Minutes, Hours, and Days.

Prerequisites​

Before enabling and configuring the duration extension feature in ODL, ensure you meet the following prerequisites:

Enabling the Duration Extension Feature in ODL​

  1. Log in to the CL portal and navigate to the required tenant (WIZ). On the left-hand side of the page, go to the On Demand Labs section.

  2. In the left menu, go to ODL (1) and click the edit (2) button.

  3. Scroll down to the Allow User to Extend Lab section and enable the checkbox.

  4. Select the required duration parameters from the dropdowns for Max Limit of Duration Extension by User. Once selected, the Allowed Extend Duration by Attendee option will be automatically chosen based on the above selection. Now, provide the appropriate duration based on your choice.

Note: The Max Limit should be an exact multiple of the Allowed Extend Duration to ensure that any extensions granted follow a consistent, repeatable pattern without remainder.

Example Calculation​

Suppose we set the following:

  1. Max Limit of Duration Extension by User = 180 minutes
  2. Allowed Extend Duration By Attendee = 30 minutes

For the setting to be valid, the Max Limit (180 minutes) should be evenly divisible by the Allowed Extension (30 minutes). Here’s how we calculate it:

Since 6 is a whole number, 180 is a multiple of 30, so this configuration is valid.

Example of an Invalid Configuration​

Now, let’s try with:

  1. Max Limit of Duration Extension by User = 175 minutes

  2. Allowed Extend Duration By Attendee = 30 minutes

Since 5.83 is not a whole number, 175 is not a multiple of 30, making this configuration invalid.

  1. Finally, click on the Submit button.

  2. To extend the duration of the lab, click on the highlighted icon at the top right corner of the page.

  3. After clicking on the icon, a confirmation pop-up will appear. Click OK to confirm the action.

  4. Finally, a confirmation message will display on the page, and a notification will be sent to your instructor.

31. Clean up for GCP Roles - (19 November 2024)​

Feature Requirement​

Implement the attendee resource clean-up for the below list.

  • GCP IAM Custom roles

Implementation:​

Developed the API calls for the cleanup of the resources in the GCP projects.

32. Loading issue on the sign-up page - (19 November 2024)​

Feature Requirement​

The sign-up page was experiencing loading issues, causing it to get stuck when users attempted to sign up through the custom portal.

Implementation​

The issue was resolved by identifying and addressing a backend error that was preventing the sign-up page from loading properly.

33. Issue with the Custom Portal Login Button - (19 November 2024)​

Feature Requirement​

The custom portal login button was not functioning as intended. When users clicked the button, the login button didn't work, preventing access to the portal.

Implementation​

The issue was resolved by identifying a backend error that was causing the login button to behave unexpectedly.

34. Grammar Check - (19 November 2024)​

Overview​

The goal is to ensure that common mistakes like spelling errors, incorrect sentence structure, and punctuation issues are identified, providing a smoother and more professional user experience.

Prerequisites​

Before checking the grammar in the custom portal, make sure the following prerequisites are in place:

Checking Grammar​

  1. Log in to the Wiz Custom portal and navigate to the Catalog section. Then, click on the required lab and press the Launch button.

  2. Once the deployment is complete, the following output will be displayed: