$ cat /etc/certs.conf
# you worked hard for that cert. you get credit for it here.
# prove it once. the credit is permanent.
a verified security certification earns points toward your rank and a permanent boost on every order after it. you verify on your account page, through the credential your provider already issued you. this page explains what you get, how the check works, what we keep, and which certifications we can verify today.
// jump to: what you get · how verification works · what we keep · the rules · supported certifications
// WHAT YOU GET
>points, once: every verified certification pays points by its level, the moment it verifies. those points count toward your rank like any other points.
foundational20 pts · +2% boost
associate40 pts · +4% boost
professional60 pts · +6% boost
expert80 pts · +8% boost
master100 pts · +10% boost
>cert boost, forever: extra points on every future order, equal to the cert's points divided by ten (a 60-point cert is a 6% boost). boosts from several certs add up, partner providers count one and a half times, and the total boost is capped at 100%.
>example: two professional certs and one expert cert are 200 points on the day they verify, and every order after that earns 20% more points than it otherwise would.
// HOW VERIFICATION WORKS
we never ask for a certificate pdf or a screenshot. verification goes through the provider's own record of your credential, so it cannot be faked, and it happens on your account page under certs.
comptia, and other credly badges
>paste the public url of your credly badge and the email address the badge was issued to. we check the badge against credly, then send a one-time code to that address. enter the code and the cert is verified.
offsec
>same idea, through accredible: the public url of your offsec credential plus the email it was issued to, confirmed with a one-time code sent to that address.
hack the box
>generate an api token in your hack the box settings and paste it. we read your rank or your completed pro labs from your profile, verify, and discard the token. it is used for that one check and never kept.
>the badge or credential email can differ from your operator brewing login email. the code goes to the address on the credential, because that is what proves it is yours.
// WHAT WE KEEP, AND WHAT WE NEVER KEEP
>kept: the certification name, the provider, its level, the points it paid, and the date it verified. that is what shows on your account page and what your boost is computed from.
>never kept: your hack the box api token, the credly or accredible email, the one-time code, and the badge details. they are used once during verification and discarded. they never enter a url, a cookie or browser storage.
// THE RULES
>verify as many certifications as you hold. there is no limit.
>each individual badge or certificate can only be linked to one account. when you verify one we check that it has not already been registered to another account, and a credential that has is refused.
>a credential the provider revokes or expires does not count. one that is not valid yet does not count either.
>the catalog on this page is the set we can verify today. an entry marked catalog only has no supported verification method yet; when one lands, it starts paying.
>certification points follow the same program rules as every other point: no cash value, not transferable, and the
terms apply.
// SUPPORTED CERTIFICATIONS
// these certification names belong to their providers. we are not affiliated with, endorsed by or sponsored by any of them; we only check that you hold the credential. the terms have the full notice.
// the supported catalog is read live from each provider. sign in to verify yours.
// ready to verify?
sign in and open certs on your account page. no account yet?
enlist.
// drink responsibly. pwn responsibly.