<aside> 💡 If you have any questions or need any help, please ask on Discord (faster response) or via email at [email protected] (slower response). For the fastest response, please first check the documentation below as it may answer your question(s).

</aside>

FAQ

🌎 Labs only work in us-east-1 (or global where relevant)!

Please check the region you are operating in or trying to launch resources into. If you are getting access denied, that is the most likely reason why! We restrict region access by design and as a security best practice.

I’m seeing a bunch of errors in my lab account

I can’t login to the lab account environment

<aside> ✅ Make sure you are in the us-east-1 (N. Virginia) region! We block access to all other regions. If you are in the correct region, then seeing some error messages is completely normal, as long as you are still able to complete the lab’s objectives and scenarios. To prevent lab abuse, we have to provide the least privileges possible, which is what causes AWS to show all of those errors you’re seeing. Unfortunately, there’s not much else we can do about that since that’s how AWS shows permission errors.

</aside>

<aside> ✅ The most common reason for this happening is a password manager. Even if it looks like you have the correct credentials entered, sometimes password managers change the values when you hit submit, causing an incorrect login. To check this, please try a different browser. Please also triple check that values you are copy/pasting.

</aside>

Can I maintain progress between lab environments?

<aside> ➡️ No. Lab environments get completely wiped after they expire or after you terminate them. Your work will not persist across lab environments. These labs are meant to be used for specific learning purposes as throw-away accounts, not to run production or personal AWS workloads.

</aside>

🚨 What am I NOT allowed to do in 🧪 Cybr Labs?

🧪 Cybr Hands-On Labs are meant to be used as learning environments only. The following actions are strictly forbidden:

• Crypto mining of any kind (unless the lab is explicitly created to demonstrate this type of attack, in which case it will be very clear in the lab’s instructions)
• Performing illegal activities including but not limited to: DDoS, spam, going after resources you do not have explicit permissions for, violating another service or organization’s ToS, hosting or processing stolen data, uploading/using stolen data or tools, etc…
• Attempting to break out of our security policies beyond the lab’s scenario: if you accidentally come across a weakness in our policies, please report at [email protected]

If you purposefully abuse our labs (even if doing something not listed above), and depending on the severity of the incident, your account may be banned and you will not receive a refund for your membership.

We actively monitor actions taken in our lab environments to prevent abuse and to better troubleshoot issues.

ℹ️ 🔎 We actively log and monitor activity in our Labs environments

Do not put or use any real secrets or sensitive information (including PII) in our lab environments! Actions are logged and monitored by us, which means we may see your secrets and/or sensitive information. We do this to prevent abuse and to better troubleshoot issues, as our labs are strictly meant for educational purposes.