Sequence - Identity Document

QuantstampCode version: not recorded (see the report)

Quantstamp reviewed Sequence (Sequence - Identity Document) on 2 Dec 2025: 30 findings, 0 critical; 25 marked fixed, 5 acknowledged.

No open critical findings
Open the reportOpen Sequence’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings46

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High009
Medium0114
Low042

Marked Informational by the firm. Not counted as findings.

InformationalBind HTTP Server to a Specific Network InterfaceAcknowledged

The HTTP server is instantiated using `http.ListenAndServe(":9999", svc)` (`/identity-instrument-master/cmd/builder-mock/main.go`, line 11\) in Go, which binds the server to all available network interfaces (`0.0.0.0`). This means the service is accessible from any network the host is connected to, including public or unintended internal networks, depending on the host's network configuration and firewall settings. This broad exposure increases the attack surface unnecessarily and may lead to unintentional service discovery, unauthorized access attempts, or abuse if firewall rules or access controls are misconfigured or absent. Binding to all interfaces is appropriate only in explicitly controlled environments (e.g., behind a reverse proxy or inside a secured container network), and even then, least-privilege design dictates narrowing exposure whenever possible.

InformationalCapture and Persist Operating System Logs Past the Lifetime of a ContainerAcknowledged

In linux systems, important operating system logs are stored in the `/var/log` subfolder. This folder should always be made available to the host through a volume, so that log tracking and log analysis systems can capture them.

InformationalConsider if Auth Key Maximum Ttl (90 Days) Is NeededAcknowledged

The current implementation allows authentication keys (`auth_key`) to have a maximum time-to-live (TTL) of up to 90 days. Long-lived credentials significantly increase the risk window for attackers: if the `auth_key`'s private key is leaked, phished, or otherwise compromised, it can be used for up to 90 days without requiring re-authentication. This undermines the security posture of the system, especially for sensitive operations or high-value accounts. Consider if 90 days TTL is needed; otherwise, consider lowering it to a week.

InformationalDo Not Mount the Host's `docker.sock` for Any Docker ContainerAcknowledged

It is possible to mount the `docker.sock` interface to a container. This enables the 'Docker within Docker' scenario, but also poses a security risk, since common Docker operations on the host are then exposed to the container.

InformationalDocker Compose Requires Logging Size ProtectionAcknowledged

Each Docker container is producing logs, which can be accessed via the command `docker logs <CONTAINER_ID>`. These logs grow over time, and it is recommended to limit the log file sizes in the Docker system and rotate them. The recommendation is to limit the number of files by 10, and let each file be at most 200MB big.

InformationalDocker Containers Run Their Commands as RootAcknowledged

When creating a Docker container, it is possible to set the user who is actually running the application and any command on the container. It is important to specifically use the `USER` directive in any Dockerfile to ensure that the user is not root and has unnecessary privileges.

InformationalDocker-Compose Should Have a Restart Policy SpecifiedAcknowledged

The user should always specify the way containers are supposed to behave when an error is encountered. One mechanism is by specifying the restart policy. For each container, it is best practice to specifically set the `restart` key.

InformationalEnable Bucket Logging for S3 BucketsAcknowledged

Logging access to any resources is a vital pillar for security. Hence, it is important that every S3 Bucket resource is set up with a proper logging configuration.

InformationalEnable Versioning on S3 BucketsAcknowledged

S3 buckets allow for versioning of the objects stored in it, and it is generally recommended to enable it since it allows access to historical versions of objects. In older versions of Terraform, this was done inline within the bucket resource definition. This inline definition is deprecated in favor of an external resource definition. This check catches the use of the deprecated method.

InformationalEnsure to Have a Backup Plan for Ec2 InstancesAcknowledged

When using EC2 instances, it is recommended to ensure that the attached EBS volume is being backed up regularly.

Show 6 more
InformationalHave Healthcheck Parameters in DockerfilesAcknowledged

Dockerfiles have an instruction called `HEALTHCHECK`. It enables a user to define a command to figure out if the program(s) running inside the container are working properly. It is generally advisable to have healthchecks in place to assist monitoring of running containers.

InformationalNon-Secp256k1 Signers Should Be Rejected Early OnAcknowledged

Non-secp256k1 signatures are not supported in the system, but are currently rejected only at the `CompleteAuth` stage.

InformationalPin Versions of Packages Installed in a Docker ImageAcknowledged

One desirable goal of docker images is that changing their Docker-files and re-building them in the future does not cause issues unrelated to the new changes. One way an image may not build in the future is if the Dockerfile contains instructions to install a certain program/library without pinning the version.

InformationalRoot Port Usage Increases Attack SurfaceAcknowledged

Ports should fall within the 0-65535 range. However, both the ingress proxy and the identity instrument services do not enforce a range. The usage of non-root ports, i.e., those less than 1024, is not enforced either. This means that both binaries must be executed with root privileges, increasing the attack surface.

InformationalServe OWASP Recommended Headers with Each RequestAcknowledged

The custom-built proxy (`/identity-instrument-master/cmd/ingress-proxy/main.go`) fails to set several critical HTTP response headers recommended by OWASP for web application security. These headers are intended to instruct browsers on how to behave when rendering content, limiting the attack surface for common exploits like XSS, clickjacking, MIME-sniffing, and resource abuse. Since this is a custom proxy implementation, these protections must be explicitly coded in, unlike in production-ready reverse proxies (e.g., NGINX or Envoy) where secure defaults or plugins are available. Without these headers, end-user browsers are left to infer behavior on their own — potentially enabling risky defaults that attackers can exploit, especially when serving dynamic or unauthenticated content.

InformationalSet Limited Capabilities for Containers in Docker ComposeAcknowledged

Containers are spun up with operating system level capabilities, and the default set is most of the time above the needs of that specific container.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Sequence’s security record

Sequence
Audits3 audits by 1 firmLast audit Dec 2025, by Quantstamp.
Critical findingsNo open critical findingsAcross 3 reports.
Open Sequence’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us