| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.PRT.001 | Latest WCAG guidelines and associated success criteria should be met by all websites and web portals (http://www.w3.org/TR/WCAG20/ ) |
Recommended |
| EGIF.PRT.002 | W3C web and mobile guidelines and best practices (http://www.w3.org/Mobile/ ) |
Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.BPI.001 | Use UML (latest version) which is a language for specifying, constructing and documenting the artifacts of software-intensive systems | Recommended |
| EGIF.BPI.002 | Use SoaML which extends the unified modeling language (UML) to enable the modeling and design of services within a service-oriented architecture. | Recommended |
| EGIF.BPI.003 | Use BPMN (latest version) which provide a notation that is readily understandable by all business users, from the business analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes and finally, to the business people who will manage and monitor those processes. | Recommended |
| EGIF.BPI.004 | Use BPEL4WS which is a Business process execution language for web services - a language for the specification of business processes and business interaction protocols. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.DEI.001 | XML and JSON with related schemas should be used for data integration. | Mandatory |
| EGIF.DEI.002 | UML, RDF and XML for data modelling and description languages. | Recommended |
| EGIF.DEI.003 | Use XSLT - XSL Transformations - a language for transforming XML documents into other XML documents. | Recommended |
| EGIF.DEI.004 | Compliance with JMS for all J2EE MOM. | Recommended |
| EGIF.DEI.005 | An XML, JSON or CSV output should be provided for forms data entry. | Mandatory |
| EGIF.DEI.006 | Use ISO/IEC 11179-3:2013 for specification and standardization of data / meta data elements. | Recommended |
| EGIF.DEI.007 | Use ANSI HL7 Health Level Seven Standard - Application Protocol for Electronic Data Interchange in Healthcare Environments. | Recommended |
| EGIF.DEI.008 | Use ebXML Standard Message Service Specification for security and reliability extensions to SOAP. | Mandatory |
| EGIF.DEI.009 | Use ISO15022 - XML Design rules to support design of message types and specific information flows. | Recommended |
| EGIF.DEI.010 | Use UN/EDIFACT - Electronic Data Interchange for Administration, Commerce and Transport. The United Nations EDI standard. | Recommended |
| EGIF.DEI.011 | Use XBRL Meta Model - eXtensible Business Reporting Language - an XML language for business reporting. | Recommended |
| EGIF.DEI.012 | Use XMI - XML Metadata Interchange Format. An open information interchange model. | Recommended |
| EGIF.DEI.013 | Use XSL - eXtensible Stylesheet Language - A family of recommendations for describing stylesheets for XML document transformation and presentation. | Recommended |
| EGIF.DEI.014 | Use ER Diagrams - Entity-Relationship diagram - a diagramming notation used in data modeling for relational databases. | Mandatory |
| EGIF.DEI.015 | Use XML schema Parts 0-2:2001 - An XML-based language for defining the structure of XML documents and for specifying datatypes for attribute values and element content. | Recommended |
| EGIF.DEI.016 | Use ISO 3166 Code Lists - 2-letter and 3-letter country code representation standard. | Recommended |
| EGIF.DEI.017 | Use ISO 8601 - Date and time representation standard. | Recommended |
| EGIF.DEI.018 | Use WCO Data Model | Recommended |
| EGIF.DEI.019 | Use REST API with JSON following security standards using OWASP | Recommended |
| EGIF.DEI.020 | Use metadata for content management. | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.SRV.001 | Use REST API or SOAP for web service invocation and communication | Recommended |
| EGIF.SRV.002 | Description of all web services using REST with JSON or WSDL (latest). The web services description language describes web services in a way that other systems can consume the services | Recommended |
| EGIF.SRV.003 | WS-I Basic Profile or Web Services interoperability profile is a set of non-proprietary web services specifications along with clarifications and amendments to those specifications that promote interoperability. | Recommended |
| EGIF.SRV.004 | WS-I simple SOAP binding profile defines the use of XML envelopes for transmitting messages and places constraint on their use. | Recommended |
| EGIF.SRV.005 | WS-I Attachments Profile defines MIME multipart / related structure for packaging attachments with SOAP messages. | Recommended |
| EGIF.SRV.006 | Registration of all web services using Universal Description, Discovery and Integration (UDDI latest version) registry. | Recommended |
| EGIF.SRV.007 | Use of hypertext transfer protocol (HTTP latest) and HTTPS as the application level communications protocol for web services. | Recommended |
| EGIF.SRV.008 | Use of LDAP v3-compliant directory for authentication, authorization, and storage of identity profiles and ID management information | Recommended |
| EGIF.SRV.009 | Use latest version of ebXML Message Service Specifications, ebXML Registry Information Model and ebXML Registry Services Specifications as an addition to UDDI registry. | Recommended |
| EGIF.SRV.010 | Use of TLS v1.3 for encryption | Recommended |
| EGIF.SRV.011 | Use of integration adaptors across organizations | Recommended |
| EGIF.SRV.012 | Selection of adaptors that are certified by the application or middleware solution | Recommended |
| EGIF.SRV.013 | Use Domain Name Service (DNS) for mapping between domain names and IP addresses | Mandatory |
| EGIF.SRV.014 | Use Dublin Core Standard to facilitate discovery of electronic resources. | Recommended |
| EGIF.SRV.015 | Use OAI harvesting protocol version 2 from Open Archives Initiative supports access to web-accessible material through interoperable repositories for metadata sharing, publishing and archiving. | Recommended |
| EGIF.SRV.016 | Use RDF - Resource Description Framework for specifying syntax of metadata used to exchange meta data by W3C | Recommended |
| EGIF.SRV.017 | Use ODRLv2.2- Open Digital Rights Language supports use of digital assets in the publishing, distribution and consumption of content, applications and services | Recommended |
| EGIF.SRV.018 | Use XrML v2.0 or eXtensible rights Markup Language is XML-based language for digital rights management (DRM) | Recommended |
| EGIF.SRV.019 | Use OpenGIS Web Map Service Interface Standard (WMS) for GIS systems (http://www.opengeospatial.org/standards/wms ) | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.SEC.001 | Use REST API security standards following OWASP. | Mandatory |
| EGIF.SEC.002 | Use OAUTH 2.0 for API authentication. | Mandatory |
| EGIF.SEC.003 | Use WS-Security to ensure security of messages transmitted between web services components | Mandatory |
| EGIF.SEC.004 | Use WS-I Basic Security Profile (Latest Version) to ensure security of messages transmitted between web services | Recommended |
| EGIF.SEC.005 | Use X.509 international standard for digital signature certificates | Mandatory |
| EGIF.SEC.006 | Use SAML - Security Assertions Markup Language (SAML) which is a XML-based framework for web services that enable exchange of authentication and authorization information. | Recommended |
| EGIF.SEC.007 | Use S/MIME ESS (Latest Version) which is a standard that extends the MIME specifications to support signing and encryption of email transmitted across internet | Recommended |
| EGIF.SEC.008 | Use XML-DSIG which is a XML compliant syntax used for representing the signature of web resources and procedures for computing and verifying such signatures | Recommended |
| Standard id | Standard | Clasification |
|---|---|---|
| EGIF.TECH.001 | Within the GoB, use intrinsic security provided by Bangladesh Computer Council Intranet (Government Networks) which need to be considered for all Government offices. | Mandatory |
| EGIF.TECH.002 | National Data Center need to be considered for hosting of Government data. Exceptions for establishing DC / DR for independent entities will be made on case-to-case basis. | Mandatory |
| EGIF.TECH.003 | All entities need to adhere to DSA and BGD e-GOV CIRT security guidelines | Mandatory |
| EGIF.TECH.004 | For inter-ministry system related information exchange, use BNDA e-Service Bus for secured transfer. | Mandatory |
| EGIF.TECH.005 | For all Government transactions requiring citizen online identity verification, BNDA e-Service Bus based authentication services need to be used. | Mandatory |