Services

What we do, in detail

Three delivery services and three assessments for Salesforce in Government Cloud. Each one shows a sample deliverable on a fictional org.

Delivery

Build it, ship it, keep it running.

01 · Implementation

Architected for the boundary first

We scope inside FedRAMP High from session one. Parity gaps surface in week one, not in UAT.

  • GovCloud from session oneData model and sharing built for the authorized boundary
  • Capture-to-award pipelineOpportunity, proposal and contract flow your program office can defend
  • CPQ and contract vehiclesPricing, vehicles and ceilings modelled the way you actually sell
  • Legacy migrationCRM and spreadsheet history moved with lineage intact
architecture.decisionsSample
Architecture decision logAcme Aerostructures (fictional)
ADR-07Opportunity and Contract set to Private; access by program roleDecided
ADR-08CUI fields sit behind one permission set, off default layoutsDecided
ADR-09Legacy CRM history loaded with source IDs kept for lineageDecided
ADR-10Planned AppExchange package not usable in the boundary; Flow insteadOpen
Sample on a fictional org. Client deliverables use this format.
02 · ISV & custom development

Built to pass the security review

Apex, integrations and data at volume, written to survive AppExchange review.

  • Apex, LWC, SOQLServer-side engineering and query optimization at scale
  • Managed package architectureNamespace, versioning and upgrade path decided up front
  • AppExchange review prepFindings closed before the submission, not after
  • ERP, PLM and gov APIsIntegration contracts documented and monitored
security-review.readinessSample
AppExchange security review readinessAcme Aerostructures (fictional)
Code AnalyzerNo high findings; two medium findings triagedClear
CRUD / FLSQueries run in user mode across the packageClear
CalloutsNamed credentials only, no secrets in codeClear
False positivesWrite-up drafted for two scanner findingsOpen
Sample on a fictional org. Client deliverables use this format.
03 · Managed services

A named senior engineer, not a ticket queue

One senior DIB resource, month to month. Partner with your admin, or hand us the whole ecosystem.

  • Named senior resourceThe person who scopes the work is the person who does it
  • Release and sandbox managementChange control that survives an audit trail request
  • Org Security ReviewConfig, permissions and code checked against NIST 800-171, on a schedule
  • Roadmap and enablementYour admins get the documentation and keep it
Compare to a full-time hire ›
monthly.reportSample
Monthly report, SeptemberAcme Aerostructures (fictional)
ReleasesThree deployed, each through sandbox with approver sign-off
RequestsFourteen closed, two carried into October
SecurityOne new finding, fixed inside the month
NextField Service pilot and an admin training session
Sample on a fictional org. Client deliverables use this format.

Assessments

Three tests, not interchangeable. We tell you which one you need.

04 · Org Security Review

Most Salesforce risk is a permission, not an exploit

Read-only review of permissions, guest surface, custom code and connected apps. Every finding carries a severity, a fix and the 800‑171 control it maps to.

  • Identity and accessProfiles, permission sets and standing admin rights, tested from every persona
  • Guest and external surfaceExperience Cloud sites, public pages and OAuth scopes that answer to no one
  • Custom code and integrationsApex, LWC and connected apps read for unsafe queries and unvalidated input
  • Mapped to 800-171Findings tied to controls and re-checked for drift each quarter
security-review.findingsSample
Org Security Review findingsAcme Aerostructures (fictional)
HighThree users hold Modify All Data outside the admin profile3.1.5
HighGuest user can read Case records on the partner site3.1.22
MedConnected app with full scope, unused for 180 days3.1.1
LowSession timeout set to twelve hours3.1.11
Sample on a fictional org. Client deliverables use this format.
05 · Penetration testing

A real test, properly authorized, and the fixes that follow

Scoped and authorized in writing, then performed by us or by a specialist US‑based firm we select and manage. We own the remediation and the re‑test.

  • Who runs itOur team, or a specialist US firm we select. US persons where CUI or ITAR is in play
  • Authorized in writingRules of engagement, scope note and the Salesforce notification handled before anyone starts
  • Remediation is oursFindings become scheduled work in your org, not a PDF on a shelf
  • Re-test and closeFixes verified, and the closure evidence kept with your control mapping
pentest.scopeSample
Rules of engagement, scope noteAcme Aerostructures (fictional)
In scopePartner Experience Cloud site and its guest profile
Out of scopeDenial of service, social engineering, production data changes
WindowTwo weeks, business hours, named contacts on both sides
Sign-offWritten authorization from the org owner before testing starts
Sample on a fictional org. Client deliverables use this format.
06 · CMMC readiness

Know your score before it is on the record

Control by control against NIST SP 800‑171, ending in a scored gap list, a plan of action and assessor-ready evidence.

  • Scope and boundary firstWhich orgs, objects and integrations actually touch CUI, and which can stay out
  • Control-by-control gap listScored against 800-171, with the objective evidence each control needs
  • POA&M and SSP inputWritten so it drops into your system security plan and SPRS affirmation
  • Remediation on a calendarSequenced by risk and effort, delivered on the retainer or handed to your team

CMMC Level 1 and Level 2 do not require a penetration test; only Level 3 does. Readiness is preparation. Only a C3PAO certifies.

readiness.gap-listSample
Gap list against NIST SP 800-171Acme Aerostructures (fictional)
AC.L2-3.1.1Authorized access controlMet
IA.L2-3.5.3Multifactor authenticationNot met
AU.L2-3.3.1Audit logs created and retainedPOA&M
SC.L2-3.13.11FIPS-validated cryptography for CUIMet
Sample on a fictional org. Client deliverables use this format.

Build low. Deploy high.

Air‑gapped orgs cannot reach the internet, AppExchange or most DevOps tools. We engineer releases on the unclassified side so your cleared team can carry them across.

Parity check

Every managed package, callout and internet-dependent feature flagged before build, with an air-gap alternative.

Low-side build

Development and test in an IL5 or unclassified mirror of your org, under our CI/CD runbook.

Release packaging

Unlocked or second-generation packages, a signed-off manifest and versioned source you own.

Deployment runbook

Deploy, verify and rollback steps written for your cleared staff on the high side.

Security baseline

Org hardening and 800‑171 evidence built in, so the high-side review has nothing to chase.

Prime teaming

A small-business subcontractor with a cleared Salesforce architect. Classified access comes through the prime.4

We do not hold a facility clearance today. Teaming inquiries: sales@rocketlab.us

Built where the security review happens first

CUI handled correctly, FedRAMP boundaries respected, evidence your auditors accept.

FedRAMP High

Delivery inside the authorized GovCloud boundary.

CMMC

Control mapping and evidence trails in-platform, by a Cyber AB Registered Practitioner Advanced.3

NIST SP 800-171

CUI safeguarding across data model and sharing.

DFARS 7012 / 7010

Cloud and incident-reporting clauses respected.

ITAR-aware

Access boundaries designed for export control.

US personnel

No offshore development. DoD Secret clearance held by the principal.

The whole Salesforce surface

Not just the parts that demo well.

Sales CloudCRMService CloudCRMRevenue Cloud / CPQQuotingField ServiceSustainment Experience CloudPortalsApex & LWCCodeFlow & automationConfigMuleSoft / APIsIntegrate CRM AnalyticsReportingData CloudDataDevOps & CIReleaseManaged packagesISV

One percent, committed up front

Not a differentiator on a source selection. It is how the firm is set up to operate.

Since May 2024

Pledge 1% member

Committing profit, product and employee time: donated Salesforce architecture and engineering hours for mission-driven organizations.

1% of revenue

Stripe Climate

Permanent carbon removal through Stripe Climate, facilitated by Frontier. Removal, not offsets. Where the 1% goes ›

Start with a mission brief

Thirty minutes on your boundary, your timeline and the work. You leave knowing what it takes.