Preserve data integrity from external editing



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I'm starting to do some research on a new application for which one of the requirements is to provide safe storage. Safe in a way to prevent that the data is being altered outside the application.



The records would be filled from EF into a SQL database to maintain ease of querying. We are examining several options but are having difficult to find any online content or guidelines (or perhaps standards).



  1. We create a checksum of each row based on all fields. By reading the checksum back we can determine if the data was changed externally


  2. Encrypt the data with public/private keys. The private key however would be embedded in the application and would have possibilities to be read back; so this would need some sort of security on the application itself by a hardware dongle or such.


  3. Own file format instead of SQL server; but still no real security


  4. Use blockchain; problem is that this application would most likely run embedded with no connection to the internet.


The background of the application is to gather measurement data from field sensors but we need to ensure that after testing / measuring no one has changed the data by accident (or on purpose).



Any pointers would be helpful.










share|improve this question



















  • 2





    How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

    – Dijkgraaf
    Nov 13 '18 at 20:33







  • 1





    Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

    – Igor
    Nov 13 '18 at 20:40











  • That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

    – Martin
    Nov 21 '18 at 18:13

















0















I'm starting to do some research on a new application for which one of the requirements is to provide safe storage. Safe in a way to prevent that the data is being altered outside the application.



The records would be filled from EF into a SQL database to maintain ease of querying. We are examining several options but are having difficult to find any online content or guidelines (or perhaps standards).



  1. We create a checksum of each row based on all fields. By reading the checksum back we can determine if the data was changed externally


  2. Encrypt the data with public/private keys. The private key however would be embedded in the application and would have possibilities to be read back; so this would need some sort of security on the application itself by a hardware dongle or such.


  3. Own file format instead of SQL server; but still no real security


  4. Use blockchain; problem is that this application would most likely run embedded with no connection to the internet.


The background of the application is to gather measurement data from field sensors but we need to ensure that after testing / measuring no one has changed the data by accident (or on purpose).



Any pointers would be helpful.










share|improve this question



















  • 2





    How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

    – Dijkgraaf
    Nov 13 '18 at 20:33







  • 1





    Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

    – Igor
    Nov 13 '18 at 20:40











  • That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

    – Martin
    Nov 21 '18 at 18:13













0












0








0








I'm starting to do some research on a new application for which one of the requirements is to provide safe storage. Safe in a way to prevent that the data is being altered outside the application.



The records would be filled from EF into a SQL database to maintain ease of querying. We are examining several options but are having difficult to find any online content or guidelines (or perhaps standards).



  1. We create a checksum of each row based on all fields. By reading the checksum back we can determine if the data was changed externally


  2. Encrypt the data with public/private keys. The private key however would be embedded in the application and would have possibilities to be read back; so this would need some sort of security on the application itself by a hardware dongle or such.


  3. Own file format instead of SQL server; but still no real security


  4. Use blockchain; problem is that this application would most likely run embedded with no connection to the internet.


The background of the application is to gather measurement data from field sensors but we need to ensure that after testing / measuring no one has changed the data by accident (or on purpose).



Any pointers would be helpful.










share|improve this question
















I'm starting to do some research on a new application for which one of the requirements is to provide safe storage. Safe in a way to prevent that the data is being altered outside the application.



The records would be filled from EF into a SQL database to maintain ease of querying. We are examining several options but are having difficult to find any online content or guidelines (or perhaps standards).



  1. We create a checksum of each row based on all fields. By reading the checksum back we can determine if the data was changed externally


  2. Encrypt the data with public/private keys. The private key however would be embedded in the application and would have possibilities to be read back; so this would need some sort of security on the application itself by a hardware dongle or such.


  3. Own file format instead of SQL server; but still no real security


  4. Use blockchain; problem is that this application would most likely run embedded with no connection to the internet.


The background of the application is to gather measurement data from field sensors but we need to ensure that after testing / measuring no one has changed the data by accident (or on purpose).



Any pointers would be helpful.







c# sql database






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 20:35









Dijkgraaf

7,48592745




7,48592745










asked Nov 13 '18 at 20:31









MartinMartin

202212




202212







  • 2





    How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

    – Dijkgraaf
    Nov 13 '18 at 20:33







  • 1





    Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

    – Igor
    Nov 13 '18 at 20:40











  • That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

    – Martin
    Nov 21 '18 at 18:13












  • 2





    How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

    – Dijkgraaf
    Nov 13 '18 at 20:33







  • 1





    Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

    – Igor
    Nov 13 '18 at 20:40











  • That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

    – Martin
    Nov 21 '18 at 18:13







2




2





How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

– Dijkgraaf
Nov 13 '18 at 20:33






How about setting the permissions on the tables so that it cannot be updated? e.g. only allow INSERT & SELECT. You can do it so that your application does have permissions if needed, all others would not. P.S. you might want to tag it with the type of database you intend to use.

– Dijkgraaf
Nov 13 '18 at 20:33





1




1





Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

– Igor
Nov 13 '18 at 20:40





Like anything else you want to secure it comes down to access and access permissions to where the data is stored (the RDBMs and server's it resides on). If you do not want external modifications made then do not grant access externally and control the credentials that do have access as well as access paths to the server(s) where the data is stored.

– Igor
Nov 13 '18 at 20:40













That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

– Martin
Nov 21 '18 at 18:13





That is obviously our start; but yet our application will save data and I need to ensure that both the application and it's data are not being tempered by external sources. We will use a hardware dongle for the application but that leaves me with the data

– Martin
Nov 21 '18 at 18:13












0






active

oldest

votes












Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289054%2fpreserve-data-integrity-from-external-editing%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289054%2fpreserve-data-integrity-from-external-editing%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

Edmonton

Crossroads (UK TV series)