Skip to content
EA

If it needs evidence from several people and someone to sign it off, hand it to EA.

Browse the full library

MVSP and VSA · For software firms answering enterprise buyers

A short checklist, answered exactly as your product is built.

Enterprise buyers attach the Minimum Viable Secure Product (MVSP) checklist to a request for proposal (RFP), or send the Vendor Security Alliance (VSA) questionnaire. EA drafts each answer from your engineering documents, policies and test reports, asks the engineer who holds what’s missing, and brings the answers to your Information Security Manager to approve.

Try EA free. No card needed.

Organisations that run work on EA

The work

Short questions, with your whole product behind each one.

  • The answers live with engineering

    Single sign-on, dependency patching and how releases are built are known to the engineers shipping the next release, not to whoever received the RFP.

  • The checklist moves, and so does the product

    Both lists are revised each year, and you ship releases in between, so last spring’s answer on patching or testing may describe a build you’ve since replaced.

  • Asked at the RFP and again at contract

    A buyer reads your answers to shortlist you, then may write the same controls into the contract for your Legal Counsel to accept.

Engineering answers each control once, and the RFP goes back on the buyer’s date with answers that still hold when procurement writes them into the contract.

What EA does

From the buyer’s copy to answers engineering has checked.

Shown on an enterprise buyer’s RFP with the checklist attached.

01 / 03

  1. EA

    Lists each of the 25 controls in the buyer’s copy under the checklist’s four groups, with the return date, and marks which ones your records already show, which need evidence and which aren’t met yet. Gap Analysis 

    Your team

    The Account Executive forwards the RFP, and the Information Security Manager confirms which product it covers.

  2. EA

    Drafts each answer from your engineering documents, identity settings and test reports, with the source beside it. Where no record shows a control, it marks “Needs evidence”, sends one request per owner and follows up; where a control isn’t met yet, it drafts a plan entry for the owner to date. EA Agent 

    Your team

    The Head of Engineering attaches the external test of the current release and dates the plan for the one control not yet met.

  3. EA

    Brings the answers and the plan to the Information Security Manager, and writes the approved answers into the buyer’s spreadsheet or the supported fields of its portal. Autofill  Approvals  Browser Plugin 

    Your team

    The Information Security Manager approves, Legal Counsel reads any control the buyer proposes as a contract term, and your team returns the RFP.

Illustrative data: stage by stage

See a buyer’s checklist answered from your engineering records.

Book a demo

Next buyer

Each RFP after this one starts from approved answers.

  • The next buyer’s copy

    EA drafts the next checklist or questionnaire from the answers already approved, and asks owners only about controls that are new or have moved.

  • This year’s revision

    When the checklist is revised, EA lists the controls that changed and drafts them from your records for the Information Security Manager. A reminder you set also asks the Head of Engineering for the new external test before the last one turns a year old.

  • A plan entry falls due

    When a dated plan entry is met, its owner attaches the record, and the next buyer reads the control as met.

Illustrative data
Approval record · single sign-onLocked
Control
Single sign-on for customers’ users
Evidence
Identity settings export
Owner
Platform Engineering Lead
Approved by
Information Security Manager
Used in
Three buyers’ checklists Current

EA’s own security

Your test reports, seen by the people you choose.

A penetration test report lists the weaknesses found in your product, so it sits in a workspace your Information Security Manager controls, apart from the answers that cite it. We ran our own ISO 27001 certification on EA: read how it ran on the ISO 27001 page.

  • Hosted your way

    EA’s cloud in a region you choose, hybrid options or on-premises. Data never used to train the models EA runs on.

  • Access

    Single sign-on, which you can enforce, and an access list for each workspace.

  • Support access

    EA staff see your data only in a time-limited window you open.

  • Testing

    An independent firm runs a penetration test on EA every year.

  • Security contact

    EA’s security team is at security@eaglobal.ai.

In the demo, see an answer cite a test report its reader can’t open.

Book a demo

FAQ

Checklist questions from software firms.

MVSP is a checklist: a short list of application security controls in four groups, each marked met or not with its evidence. The Vendor Security Alliance publishes two free questionnaires instead: VSA-Core, its most critical security and privacy questions, and VSA-Full, the deeper one. Both are revised each year, buyers use either in RFPs and contracts, and EA answers either from the same engineering records.

The buyer’s security team, to shortlist you, and its procurement team, which may write the controls into the contract. Your Information Security Manager approves the answers first, and Legal Counsel reads any control proposed as a term.

Each answer cites its record. The checklist asks for an external penetration test at least once a year, so if your latest report is more than a year old or covers an earlier release, EA marks the control “Needs evidence” and asks the Head of Engineering, and nothing goes back until your Information Security Manager approves it.

Yes, from past buyers’ checklists, any security questionnaire you’ve answered, or your engineering documents as they are. Our Customer Success team helps with exports from other platforms. Plans differ by the number of autofills, the workspaces you need and the size of your knowledge library; see the pricing page.

Say so, with a date. The checklist is meant as a baseline to improve against, so EA drafts a plan entry for each control you don’t meet, and its owner sets the date before your Information Security Manager approves it.

Your next enterprise RFP, without re-asking engineering each control.

A buyer’s checklist, to your Information Security Manager.

Related solutions

By industry