Because this stage parallels the other stages of the process, you can work on this at the same time you are completing previous stages. The more progress you make on it now, the greater the probability that you may be evaluated before other participants who finish their work in a linear fashion.
This stage can also function as a kind of lifesaver for you. If you have not yet graduated, perhaps have no previous work experience, or maybe got a low score on the knowledge test, but were able to successfully finish this stage, you have the most valuable competence of all: The ability to learn new things on the fly and apply them to solve real problems. This, along with a good personality and strong values, mean more to us and our customers than anything else.
In this stage, we want you to demonstrate, through practical exercises,
your technical skills by solving problems similar to the ones you will face in
your work with
The technical challenges are divided into
With the first,
you demonstrate your skill to bypass security controls.
With the second,
you demonstrate your adaptation skill when it comes to problem-solving
in unknown environments.
With the third,
you demonstrate your proficiency and speed in understanding source code.
By solving challenges we:
Promote the solution of unresolved challenges.
Encourage self-directed and independent learning.
By uploading your solutions to
GitLab, you will be able to:
GitLabinfrastructure to analyze your efficiency and work quality as you adapt to the process.
Familiarize yourself with the tools (
Gherkin, etc) and concepts (automation, unit tests, continuous integration,
linting, etc.) that you will use in your daily work with
Allow the community and the team to view your results.
programmingchallenges, we recommend Codeabbey. Also, we suggest using a language that is not widely used.
ctf-hackingchallenges, we recommend Root Me.
After solving a challenge, immediately submit your answer. Do not save your answers to send later as a larger group submission. When you send them individually and immediately you will receive feedback that will tell you what, if anything, you did incorrectly and may help you with upcoming questions.
4. Stage steps
To successfully finish this stage, you must:
GitLabusing your personal email and the username of your choice. Your username must not exceed 12 characters in length and only contain lowercase letters and numbers.
Join our Forum, where you can interact with
Fluid Attackspersonnel and other candidates, who are working in the same stage that you are, to discuss questions or issues you may have.
Request permission to access the
Git Trainingrepository by filling out this form.
Repo Access Messagefield, paste the following message:
I have read and understood all documentation pertaining to technical challenges, I agree to all of the terms and therefore request access to the
trainingrepository with my
Request permission to access the
Writeupsrepository by filling out this form. This time around, the Repo Access Message field should have the following: Request developer permissions to the
Writeupsrepository through this .
This time around, the
Repo Access Messagefield should have the following:
I have completed three (3)
programmingand three (3)
ctf-hackingunique challenges in the training repo and therefore request access to the
writeupsrepository with my
vbd-hackingchallenges in the writeups repository.
The challenge stage ends under any of the following conditions:
You have met all objectives and sent an
If there has been no activity (
gitrepos) within 14 calendar days.
If you clearly state, via email, that you are no longer interested in continuing the process.
If you present someone else’s complete or partial solutions as your own (plagiarism).
If you solve a challenge with the help of others.
In all cases, the email address for these steps is: firstname.lastname@example.org
If you were removed from the challenge due to circumstances 1, 2 or 3, you may apply again, at any time, and start the process over by clicking here If your removal was a result of circumstance 4 or 5 you are not eligible for any future retry.
The proprietary rights of all content in the repositories are defined in the files:
The license and privileges that users of the repositories have are defined in the files:
Carrying out a
merge requestimplies the transfer of copyrights. Therefore, all information contained herein may be used by
Fluid Attacksfor any commercial purpose, always preserving the moral rights of their authors.
Making solutions easily available to everyone presents an opportunity for plagiarism. How do we show the solution and avoid plagiarism at the same time? Plagiarism is not a technical problem. Plagiarism is copying another’s work and then presenting it as your own.
To discourage plagiarism we require that the author of each algorithm is clearly stated in a centralized place. This provides clear author attribution and allows for public scrutiny in case of plagiarism.
In other words, the current model avoids plagiarism through total transparency.
Fluid Attacks applies algorithmic similarity detection techniques
to all solutions submitted. We use:
Now that you know all the rules and have a general understanding of why these challenges are important, you can proceed to the Submission guide and start posting your solutions. Good luck!