Skip to content

Embed a canary token as a trap #189

Closed

Description

@commjoen

Activity

  1. self-assigned this
    on Feb 17, 2022
  2. added 3 commits that reference this issue on Feb 24, 2022
  3. added a commit that references this issue on Mar 8, 2022
  4. added a commit that references this issue on Mar 28, 2022
  5. commjoen commented on Mar 28, 2022

    @commjoen
    CollaboratorAuthor

    @bendehaan if we want to do Challenge15 in people their own cloud the instruction would be like below, are we sure we want to do that?

    Running Challenge15 in your own cloud only

    When you want to include your own Canarytokens for your cloud-deployment, do the following:

    1. Fork the project
    2. Make sure you use the GCP ingress or AWS ingress scripts to generate an ingress for your project.
    3. Go to and select AWS Keys, in the webHook URL field add <your-domain-created-at-step1>/canaries/tokencallback
    4. Encrypt the received credentials so that Challenge15 candecrypt them again
    5. commit the unencrypted and encrypted materials to Git
    6. adapt the hints of Challenge 15 in your fork to point to your fork
    7. create a container and push it to your registry
    8. override the K8s definitionfiles.
  6. added a commit that references this issue on Mar 29, 2022
  7. bendehaan commented on Mar 30, 2022

    @bendehaan
    Collaborator

    Discussed out of band. For the record: start with a how to, possibly expand to custom (cloud?) solution later.

  8. added a commit that references this issue on Mar 30, 2022
  9. added 7 commits that reference this issue on Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions