Compliance and questionnaires

Security questionnaire answers

In reviewUpdated 2026-11-15Trust Center

In review. This record, and the tools and files it cites, are on a review branch. They are not in the main source tree yet, so you cannot check them in a copy of the main source today.

Pre-written answers for the common sections of vendor security questionnaires (SIG Lite, CAIQ, HECVAT style) for Aster, a data-free, on-premises, in-process library (SDK and examples under the MIT licence, runtime under the Aster Runtime EULA), maintained by a company.

Read first. Aster is software that a customer links into their own application. We do not host it, receive data from it or run a service for it. Where a question assumes a hosted service, customer data or a SaaS, we mark it N/A and give the reason. Answers are accurate as of 2026-11-11 and link to evidence; where a control is not in place we say No or Planned. These are not the official forms: copy the answers into the customer's form and keep the evidence links. Company details are to be decided. The software is licensed under MIT (LICENSE) and comes without warranty or service level.

1. Company and product

QuestionAnswer
MaintainerBarnyard Greens LLC (Pennsylvania, USA). A dedicated spin-off entity is planned
Product and deliveryAster UI: CPU rendering and UI toolkit, delivered as compiled binaries with signed release records; the source is private
HostingNone. Runs in the customer's process
LicensingSDK and examples MIT; runtime under the Aster Runtime EULA (free, redistributable with your application)
Open source?The SDK and examples, yes (MIT). The runtime, no: the source is private. Third-party notices: THIRD-PARTY-NOTICES.md

2. Data handling and privacy

QuestionAnswer
Does the product collect, store, process or transmit customer data?No. It processes the data the host application passes in, in memory, and returns results. No telemetry, no network in the default build, no files written in the default build. No data: what Aster does and does not do, checkable with tools/trust/no-io-check.sh
Personal data (GDPR, CCPA)N/A for the software: we are not a processor of customer personal data through the product. We hold no user data through the software; any contact details you send us (for example in a security report) are used to answer you
Sub-processorsN/A
Data location, residency, retention, deletion, backup of customer dataN/A: we hold none
Does the product call home, check licenses online or update itself?No
Cross-border transfersN/A
Privacy by designYes: data-free by construction; I/O features are off by default

3. Security governance

QuestionAnswer
Security policySecurity policy (reporting, scope, targets), CONTRIBUTING.md (internal rules)
Dedicated security staffNo. A small team with one human maintainer; the security lead function is held by the maintainer
Independent certifications (SOC 2, ISO 27001)None. Not planned; the product holds no customer data. An assessor can review the release records (SBOM, provenance, VEX); source access is not offered.
Penetration testNo third-party test to date. Planned; the fuzzing plan is Fuzzing
Security trainingNo formal programme
Risk assessmentInformal. CRA-style risk assessment planned (EU Cyber Resilience Act readiness)

4. Secure development (SSDF, SDLC)

QuestionAnswer
Secure development frameworkMapped to NIST SSDF with gaps stated: SSDF mapping and draft attestation
Code reviewReview branches, protected main, independent review pass for significant changes, human review for security-sensitive changes (Provenance and AI use)
AI-generated codeYes, most code is written by AI agents under human direction; policy and copyright caveat in Provenance and AI use
Static and dynamic analysisclippy with warnings denied on every change; fuzzing and Miri planned (Fuzzing, Unsafe code policy and inventory)
Memory safetyRust. unsafe_code is forbidden in the core crates (rust/Cargo.toml); unsafe inventory in Unsafe code policy and inventory
Separate dev, test, production environmentsProduction N/A (no service). Builds run in isolated containers
Secrets management in codeRule in CONTRIBUTING.md; automated secret scanning planned
Developer background checksN/A / not performed

5. Supply chain and third parties

QuestionAnswer
SBOMGenerated per release: Supply chain: SBOM, licences, advisories, vetting, reproducibility
Third-party components and licensesFew; locked in rust/Cargo.lock; licenses in THIRD-PARTY-NOTICES.md; default core graph checked by tools/trust/no-io-check.sh
Vulnerability monitoring of dependenciesPlanned, Supply chain: SBOM, licences, advisories, vetting, reproducibility
Signed releases, provenancePlanned, Releases: signing, provenance and verification
Reproducible buildsInternal check; not published
Vendors with access to systemsNone for the product

6. Vulnerability and incident management

QuestionAnswer
Vulnerability disclosure policySecurity policy, Vulnerability handling policy
Severity scoringCVSS v4.0
Patch timelinesCritical 30 days, high 60 days targets, from confirmation
Customer notification of vulnerabilitiesPublic signed advisories and release notes; CVE where eligible
Regulatory reportingEU CRA Art. 14 readiness described in Vulnerability handling policy; open items listed there
Breach historyNone known. The product holds no customer data, so a product breach would be a supply-chain event: compromise of our build or distribution
Incident response planDefined in Vulnerability handling policy for product vulnerabilities; no separate corporate IR plan document

7. Access control, encryption, infrastructure

QuestionAnswer
Customer user authentication, SSO, MFA, RBACN/A: no accounts or service
Encryption of data at rest / in transitN/A for customer data (none held). The optional net-sync transport is unencrypted by design; use TLS or a VPN around it (No data: what Aster does and does not do)
Cryptography in the productNone (Export control self-assessment)
Network security, firewalls, WAF, DDoSN/A: no hosted service
Logging and monitoring of the serviceN/A. Developer-side logging of repository access: not formalized
Physical security, data centersN/A: no data centers. Development hosts are privately operated, not cloud-hosted
Multi-tenancy, tenant isolationN/A

8. Business continuity and resilience

QuestionAnswer
Service availability, RTO/RPO, SLAN/A for the product (runs on the customer's side). No service level is offered; engineering targets are in Support and versioning policy
Disaster recovery of source and releasesSource and releases are backed up by us; backup restore is not documented here. Released binaries stay available in the release archive.
Key-person riskYes, a real limit: one human maintainer; no source escrow is offered.
Product support lifecycleSupport and versioning policy, EU Cyber Resilience Act readiness
End-of-life noticeStated per major version in release notes
QuestionAnswer
Export controlSelf-assessment likely EAR99, no crypto: Export control self-assessment
EU CRAManufacturer obligations mapped: EU Cyber Resilience Act readiness
Accessibility (WCAG, VPAT)The toolkit has an accessibility layer in aster-appkit (app/a11y.rs) and an accessibility gate across themes in aster-blueprint. No VPAT or third-party conformance report exists
HECVAT, PCI, HIPAA, FedRAMPN/A: no hosted service and no regulated data; no certification held
Right to auditNo right to audit the source; release records are public (SBOM, provenance, VEX).
Subcontractors and offshoringDevelopment uses AI coding agents; details in Provenance and AI use
Insurance, indemnification, liabilityThe Aster Runtime EULA provides the software as is, without warranty, and limits liability. No indemnification is offered.

Source docs/trust/QUESTIONNAIRE.mdlast changed 2026-11-15

More records

Every record in the Trust Center is public.