applied-cryptography/appliedcrypto
1
0
Fork 0
mirror of https://github.com/billbuchanan/appliedcrypto.git synced 2026-02-20 13:50:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Bill Buchanan
2025-01-13 21:47:27 +00:00
committed by GitHub
parent ccba85a6e1
commit b566f92646
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
z_assessments/coursework/README.md
View File

@@ -1,7 +1,7 @@
![esecurity](https://raw.githubusercontent.com/billbuchanan/esecurity/master/z_associated/esecurity_graphics.jpg)
# Analysis of Next Generation Cryptography
The coursework hand-in date is: **Sunday, 12 May 2024**. There will be a hand-in in Moodle for your submission. **Note: there is no need to write your own code for the method(s) investigated, as it will typically involve running standard code from GitHub sources.**
The coursework hand-in date is: **Sunday, 11 May 2025**. There will be a hand-in in Moodle for your submission. **Note: there is no need to write your own code for the method(s) investigated, as it will typically involve running standard code from GitHub sources.**
## Use of AI tools
At the end of your coursework document submission, please include a short declaration that the submission is your own work. If possible, try not use AI tools to generate any part of your work. If you do, all the content which has been generated by an AI tool should be acknowledged and highlighted in your submission, with an appendix containing the prompts input to the tool and responses you have received.
@@ -17,14 +17,14 @@ You are requested to investigate, build a prototype, and evaluate one of the fol
* **Key Distribution Centres**. The complexity of handling keys is an increasing challenge for many companies. Within a KDC, we can implement methods which will generate encryption keys for users. This topic will involve investigating possible methods that could be used.
* **Blockchain integration**. Many applications are moving towards storing data on a blockchain and in using smart contracts. This area will investigate new areas of improving the security and/or performance of blockchain related methods.
* **Tokenization**. There is a vast increase in the usage of tokens to either protect sensitive details or provide one-time access. This area will allow you to investigate different tokenization methods, such as using Ferrnet tokens or some of the security weaknesses of OAuth 2.
* **IPFS (Interplanetary File System)**. This breaks files into chunks and then distributes them around the world and where we can integrate version control on files. Overall it has advances in reducing latency, improving resilance, and avoiding censorship.
* **IPFS (Interplanetary File System)**. This breaks files into chunks and then distributes them around the world and where we can integrate version control on files. Overall, it has advanced in reducing latency, improving resilience, and avoiding censorship.
* **Passwordless systems**. This supports MFA using biometrics, NFC, and BLE, and supports FIDO2 using public key encryption.
* **Privacy-Preserving Machine Learning**. With this we can use cyptography methods to preserve the privacy of our data for machine learning applications.
* **Privacy-Preserving Machine Learning**. With this, we can use cryptographic methods to preserve the privacy of our data for machine-learning applications.
There are many different methods involved in each of these areas, so while your literature review might have a relatively wide scope, you might want to focus in on one or more methods for your implementation and evaluation. You may also pick another related area, but this would have to be approved by your tutor.
## Tasks
You should pick one of the areas defined, and then:
You should pick one of the areas defined and then:
* **Perform a literature review around the required application area**. This will involve using sources such as Google Scholar and outlining some of the key research in the area.
* **Produce a basic prototype of your application area**. This might involve gathering code from GitHub sources, and/or creating your own code. Make sure you keep the references to any code you have used.