Sanctum SecOps LLC
Registered address
128 Dry Run RdPine City, NY 14871USDirect
- Telephone +1 (607) 378-8287
- Email [email protected]
- Apex https://www.sanctumsecops.com/
Founder Brian Vicente — ORCID 0009-0006-6395-5308
Contact
One company record. Every value on this page reads from it.
Name, address, telephone, email and federal identifiers are rendered from the canonical identity module rather than typed into this page. That is why the address here agrees with the address in a capability statement, a federal registration and a certificate subject — there is only one place any of them can be changed.
Canonical source
Federal identifiers
| Identifier | Value | Used for |
|---|---|---|
| Unique Entity ID | H3A2Z4R3HE87 | SAM.gov registration identifier. Required on federal forms. |
| CAGE code | 20XS3 | Commercial and Government Entity code. |
| DUNS | 145042588 | Legacy identifier, still requested on some forms. |
| EIN | 42-2733487 | Employer Identification Number for the LLC of record. |
The LLC is the sole registrant and the sole federal contract signatory. The three Delaware corporations do not hold their own registrations.
Routing
Four kinds of enquiry, and what to include in each
The include list is the difference between a first reply that answers the question and a first reply that asks four of its own.
Engagement scoping
A migration, a PKI build, a CMMC readiness assessment, a fractional CISO retainer, or anything that will end in a statement of work.
Include
- The certificate profile you issue today, or the hostname and device-class inventory you have to cover
- Whether an existing hierarchy is being extended or a new one is being designed and keyed
- Whether the output has to satisfy an external assessor, since that changes what counts as done
- Any date you are working against, and what happens if it slips
What happens next
A written scope document naming what is inside and outside the boundary, then a quote against that document. Scoping is unpaid.
Production incident
A trust failure in something already running: issuance down, suspected key compromise, mis-issuance, revocation that cannot be published.
Include
- What broke, when it started, and whether it is still breaking
- The affected subject names or the issuing CA, whichever is narrower
- Whether a key is suspected exposed, because that changes the order of everything else
- Who on your side has authority to approve a revocation
What happens next
If you hold a retainer, use the contact path agreed at onboarding — that is the only route carrying a response commitment. Without one, this is best effort and stated as such.
Partnership and reseller
Certificate authority partnerships, distribution, teaming on a federal opportunity, or carrying the platform under your own engagement.
Include
- The commercial shape you are proposing, in one paragraph
- Which of the five platform components it touches
- Any registration or set-aside status relevant to a teaming arrangement
What happens next
A direct answer, including a direct no where the shape does not fit.
Standards and research
The Internet-Drafts, the composite profiles, the enterprise OID arc, or a review request on published work.
Include
- The draft name or the OID you are asking about
- Whether you are implementing against it or reviewing it
- Any interoperability result you already have, positive or negative
What happens next
Correspondence on drafts belongs on the relevant IETF list where the archive is public. Direct contact is fine for anything that is not list traffic.
Limits
What email does not carry
Stated up front so a request does not have to be refused after it has already been sent.
Not by email
- Credentials, private keys and key material are never sent or received by email, and never pasted into a ticket. There is a submission path for them and it is established at onboarding.
- A production incident sent to a mailbox is a production incident nobody has been paged about. Retainer holders use the agreed contact path.
- Quotes are written against a named scope. A number quoted in a reply to an unscoped question would be a guess with an invoice attached to it.
Support requests belong on the desk
Anything with a ticket number attached goes through the service desk, where it carries a severity and a named owner. Commercial and scoping questions come here.
Sanctum SecOps LLC, 128 Dry Run Rd, Pine City NY 14871, +1 (607) 378-8287, [email protected]