Skip to main content

Guidance and regulation

Skip to results
140 results sorted by Most viewed
From Central Digital and Data Office (CDDO)
  • Apply the government secure email policy.

  • Find out what a .gov.uk Approved Registrar does, how to choose one and information about pricing.

  • Find out if your organisation is eligible for a .gov.uk domain name and what to do if it’s not.

  • Check if your organisation is eligible for a non-government domain name and how to get one.

  • Sample accessible document policy, including example wording and guidance on what to cover.

  • Publish your code and use open source to improve transparency, flexibility and accountability.

  • Configure email services securely using encryption and anti-spoofing.

  • A service must be in compliance with all applicable data privacy regulations including the General Data Protection Regulation and the Data Protection Act 2018

  • Information about the open standards chosen for use in government technology.

  • Use open standards to build technology that is easier to expand and upgrade, and make sure it communicates with other technology.

  • Make sure your technology, infrastructure and systems are accessible and inclusive for all users.

  • Keep systems and data safe with the appropriate level of security.

  • Find out who to get permission from to apply for a .gov.uk domain name.

  • Consistent and standards-based comma-separated values (CSV) files help make data more effective and easier to share across government.

  • Use the cloud first policy by evaluating cloud computing before other options.

  • What to do when your .gov.uk domain name is approved.

  • Your purchasing strategy must show you’ve considered commercial and technology aspects, and contractual limitations.

  • The objectives and supporting resources assist organisations to understand, plan and deliver an assessment for the first year goals.

  • Follow this guidance to understand how to become a .gov.uk Approved Registrar

  • Structuring, designing and publishing your API documentation