Raffles Consulting Services
Prepare an EDGE Common Criteria project by fixing the product version, security target, evaluation boundary, accredited bodies and first certification.
An EDGE Common Criteria project needs a stable target of evaluation. If the product version, included components, deployment assumptions or security functions keep changing, the evaluator and certification body may be assessing a different product from the one management expects to sell. The grant file should connect the commercial product, security target, evaluation evidence and accredited certificate without treating certification as a general endorsement of every deployment.
Freeze the EDGE Common Criteria target
Identify the legal applicant, product name, version, build, hardware dependency, firmware, interfaces, included components and excluded services. State the intended users, operating environment and assumptions. Maintain a configuration list that can be reproduced by development, the evaluator and the release team. A marketing family name is not a sufficiently precise target if customers can receive materially different builds.
The current EDGE Common Criteria activity page identifies ISO 15408 certification, a twelve-month project period, supported professional and first-year certification or testing costs, and the required accredited certificate or reports. It excludes surveillance and renewal after first-year certification, GST and software costs. The EDGE FAQ supplies common applicant and claim controls.
Align the security target and assessment bodies
Define the security problem, protected assets, threats, assumptions, objectives, security functions and assurance evidence in language that the product team can trace to requirements and tests. Record the chosen assurance level or applicable protection profile with reasons. Confirm the evaluator, laboratory and conformity assessment body roles, accreditations and quotation boundaries before commitment.
Enterprise Singapore’s page states that the conformity assessment body should be accredited by the Singapore Accreditation Council or an internationally recognised body listed in the ILAC, IAF or APAC mutual-recognition arrangements. Capture the current accreditation scope, not only a logo. Check whether subcontracted testing remains within the recognised arrangement and who issues the final certificate.
Control product changes through certification
Create a change board for code, dependency, hardware, configuration and documentation changes during evaluation. Each change should state whether it affects the target, evidence, schedule or retesting. Keep findings, corrective actions and closure evidence linked to the evaluated build. Do not release a materially different version under the certified label without the appropriate assessment.
At closeout, reconcile the vendor proposal, quotation, required SS 680 evidence where applicable, assessment-body quotation and accreditation, report, certificate, training or capability evidence, invoice and full payment. Preserve the one-year revenue and qualifying-job projections as forecasts. Use the standards certification scope guide for the wider certification workflow.
Turn the decision into a controlled file
Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.
Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.
Review before commitment and again before closeout
Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.
Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.
Handle exceptions without rewriting history
Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.
If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.
Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.
Verify the final outcome independently
Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.
Use the Singapore business support decision guide for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.
Practical review checklist
- Target of evaluation frozen
- Security target approved
- Accreditation scope checked
- Change board operating
- Certificate and payment reconciled
The EDGE Common Criteria project is controlled when the certified product version and evaluation boundary are reproducible, the assessment chain is accredited and product changes remain traceable through the final certificate.