Sign inSign up

cisagov/scanner

By cisagov

•Updated about 19 hours ago

Automated pshtt, trustymail, and sslyze scanning

Image
0

10K+

cisagov/scanner repository overview

⁠pshtt, trustymail, and sslyze Scanner

GitHub Build Status License CodeQL

⁠Docker Image

Docker Pulls Docker Image Size (latest by date) Platforms

This is a Docker container that uses domain-scan⁠ to scan domains using pshtt⁠, trustymail⁠, and sslyze⁠.

This Docker container is intended to be run via cisagov/orchestrator⁠.

N.B.: The secrets in the src/secrets directory are only used when testing via the docker-compose.yml composition. Normally this Docker container is run via the Docker composition in cisagov/orchestrator⁠, which expects the secrets in a different location.

⁠Running

⁠Running with Docker

To run the cisagov/scanner image via Docker:

docker run cisagov/scanner:1.4.0
⁠Running with Docker Compose
  1. Create a compose.yml file similar to the one below to use Docker Compose⁠.

    ---
    name: scanner
    
    services:
      scanner:
        image: cisagov/scanner:1.4.0
        volumes:
          - type: bind
            source: <your_log_dir>
            target: /home/cisa/shared
    
  2. Start the container and detach:

    docker compose up --detach
    

⁠Using secrets with your container

This container also supports passing sensitive values via Docker secrets⁠. Passing sensitive values like your credentials can be more secure using secrets than using environment variables. See the secrets⁠ section below for a table of all supported secret files.

  1. To use secrets, create an aws_config file in this format⁠:

    [default]
    aws_access_key_id=AKIAIOSFODNN7EXAMPLE
    aws_secret_access_key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
    region=us-east-1
    output=json
    
  2. Then add the secret to your compose.yml file:

    ---
    name: scanner
    
    secrets:
      aws_config:
        file: ./secrets/aws_config
    
    services:
      scanner:
        image: cisagov/scanner:1.4.0
        volumes:
          - type: bind
            source: <your_log_dir>
            target: /home/cisa/shared
        secrets:
          - source: aws_config
            target: aws_config
    

⁠Updating your container

⁠Docker Compose
  1. Pull the new image from Docker Hub:

    docker compose pull
    
  2. Recreate the running container by following the previous instructions⁠:

    docker compose up --detach
    
⁠Docker
  1. Stop the running container:

    docker stop <container_id>
    
  2. Pull the new image:

    docker pull cisagov/scanner:1.4.0
    
  3. Recreate and run the container by following the previous instructions⁠.

⁠Updating Python dependencies

This image uses Pipenv⁠ to manage Python dependencies using a Pipfile⁠. Both updating dependencies and changing the Pipenv⁠ configuration in src/Pipfile will result in a modified src/Pipfile.lock file that should be committed to the repository.

⁠Updating dependencies

If you want to update existing dependencies you would run the following command in the src/ subdirectory:

pipenv lock
⁠Modifying dependencies

If you want to add or remove dependencies you would update the src/Pipfile file and then update dependencies as you would above.

Note

You should only specify packages that are direct requirements of your Docker configuration. Allow [Pipenv] to manage the dependencies of the specified packages.

⁠Image tags

The images of this container are tagged with semantic versions⁠ of the underlying example project that they containerize. It is recommended that most users use a version tag (e.g. :1.4.0).

Image:tagDescription
cisagov/scanner:1.4.0An exact release version.
cisagov/scanner:1.3The most recent release matching the major and minor version numbers.
cisagov/scanner:1The most recent release matching the major version number.
cisagov/scanner:edgeThe most recent image built from a merge into the develop branch of this repository.
cisagov/scanner:nightlyA nightly build of the develop branch of this repository.
cisagov/scanner:latestThe most recent release image pushed to a container registry. Pulling an image using the :latest tag should be avoided.⁠

See the tags tab⁠ on Docker Hub for a list of all the supported tags.

⁠Volumes

Mount pointPurpose
/home/cisa/sharedOutput

⁠Ports

There are no ports exposed by this container.

⁠Environment variables

⁠Required

There are no required environment variables.

⁠Optional
NamePurposeDefault
AWS_CONFIG_FILEThe path to the configuration file containing the AWS credentials.null
AWS_PROFILEThe AWS profile to use.null

⁠Secrets

FilenamePurpose
aws_configAWS credentials allowing read-only access to the Elasticsearch DMARC database in this format⁠

⁠Building from source

Build the image locally using this git repository as the build context⁠:

docker build \
  --tag cisagov/scanner:1.4.0 \
  https://github.com/cisagov/scanner.git#develop

⁠Cross-platform builds

To create images that are compatible with other platforms, you can use the buildx⁠ feature of Docker:

  1. Copy the project to your machine using the Code button above or the command line:

    git clone https://github.com/cisagov/scanner.git
    cd scanner
    
  2. Create the Dockerfile-x file with buildx platform support:

    ./buildx-dockerfile.sh
    
  3. Build the image using buildx:

    docker buildx build \
      --file Dockerfile-x \
      --platform linux/amd64 \
      --output type=docker \
      --tag cisagov/scanner:1.4.0 .
    

⁠Contributing

We welcome contributions! Please see CONTRIBUTING.md⁠ for details.

⁠License

This project is in the worldwide public domain⁠.

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication⁠.

All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with this waiver of copyright interest.

Tag summary

Content type

Image

Digest

sha256:6ad3906b3…

Size

162.4 MB

Last updated

11 months ago

docker pull cisagov/scanner