<commit_before>---
layout: text/textblock
---

### [2]In Alpha stage

During [Alpha stage](/topics/service-design-delivery-process/alpha-stage/) you’ll have an understanding of the users, data and threats that affect your service. You will have established an appropriate approach to integrate relevant security and privacy measures into your design with minimal user impact.

You should:

- identify secure and private methods of generating or processing data within or between datastores, the solution and users
- identify appropriate authentication methods that are as seamless as possible to the user
- understand to what degree the solution has to comply with the [Information Security Manual](http://www.asd.gov.au/infosec/ism/) and [Protective Security Policy Framework](https://www.protectivesecurity.gov.au/Pages/default.aspx), and internal agency security policies, and create a plan on how to achieve this
- conduct a privacy impact assessment
- conduct a threat and risk assessment, and an [Information Security Registered Assessors Program Assessment](http://www.asd.gov.au/infosec/irap/index.htm) (IRAP) if appropriate
- identify potential threats to your service, including potential pathways for insider threats and hackers, and demonstrate an understanding of how to mitigate the identified threats

To support the work in Alpha you should:

- map the systems, data and responsible agencies
- understand what user data might be needed or collected by the service
- understand what existing statistical datasets may be relevant to your service and the [Australian Government principles on data integration](http://statistical-data-integration.govspace.gov.au/)
- understand which data you collect is (and isn’t) personal information and how it might be stored, accessed and disseminated
- involve relevant security professionals throughout the Alpha stage

You should understand the service requirements relating to:
<commit_msg>Use HTTPS links<commit_after>---
layout: text/textblock
---

### [2]In Alpha stage

During [Alpha stage](/topics/service-design-delivery-process/alpha-stage/) you’ll have an understanding of the users, data and threats that affect your service. You will have established an appropriate approach to integrate relevant security and privacy measures into your design with minimal user impact.

You should:

- identify secure and private methods of generating or processing data within or between datastores, the solution and users
- identify appropriate authentication methods that are as seamless as possible to the user
- understand to what degree the solution has to comply with the [Information Security Manual](https://www.asd.gov.au/infosec/ism/) and [Protective Security Policy Framework](https://www.protectivesecurity.gov.au/Pages/default.aspx), and internal agency security policies, and create a plan on how to achieve this
- conduct a privacy impact assessment
- conduct a threat and risk assessment, and an [Information Security Registered Assessors Program Assessment](https://www.asd.gov.au/infosec/irap/index.htm) (IRAP) if appropriate
- identify potential threats to your service, including potential pathways for insider threats and hackers, and demonstrate an understanding of how to mitigate the identified threats

To support the work in Alpha you should:

- map the systems, data and responsible agencies
- understand what user data might be needed or collected by the service
- understand what existing statistical datasets may be relevant to your service and the [Australian Government principles on data integration](https://statistical-data-integration.govspace.gov.au/)
- understand which data you collect is (and isn’t) personal information and how it might be stored, accessed and disseminated
- involve relevant security professionals throughout the Alpha stage

You should understand the service requirements relating to:

{'fraction_non_alphanumeric': 0.05750962772785623, 'fraction_numerical': 0.0005134788189987163, 'mean_word_length': 5.078003120124805, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 5, 'lorem ipsum': 0, 'www.': 6, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1689442', 'n_tokens_mistral': 882, 'n_tokens_neox': 845, 'n_words': 478}