ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

field level encryption?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • field level encryption?

    quote from:


    Also included in 7.1 in the security arena is column-level encryption, which gives operators the ability to target an individual column for encryption without changing the underlying application or any code.
    The above was in a paragraph about XML

    from iTech Solutions News Letter


    Column Level Encryption
    • No application changes required
    • Clients and ISVs can easily encrypt sensitive data
    • Encrypt a specific column in a database table
    • Encryption algorithms from solution providers including Patrick Townsend, Linoma Software, and Protegrity
    What is this....dds/sql/xml?
    Where can I find more detail?


    Thanks
    GLS
    The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

  • #2
    Re: field level encryption?

    DB2/400 (the name most users continue to use) also gains new column-level encryption capabilities that will allow developers to encrypt large swaths of data within DB2/400, without getting their hands dirty with low-level programming. IBM is actually providing API hooks for encrypting the columns via native database-level access or via SQL, and the encryption algorithms themselves will be provided by third-party tool vendors.

    Currently, Patrick Townsend Security Solutions and Linoma Software are the only third-party providers who have committed to delivering this encryption capability when i/OS 7.1 becomes available next week, although other tools vendors--as well as application developers--are expected to deliver them in the future.

    "These [encryption capabilities] are not in the operating system itself, which means you sign up to get the updates from these other providers," Jarman says. "This really simplifies how you would encrypt columns in a database without actually doing it within the application programming itself, which is how you would do it today. This should be very valuable to a lot of people."

    After months of speculation, IBM today formally made its announcement for the version 7.1 release of i/OS, which will become available Friday, April 23. The new release brings lots of goodies in a variety of areas, including enhancements to the PowerHA high availability software, native support for storing XML and column level encryption in DB2/400,
    "Time passes, but sometimes it beats the <crap> out of you as it goes."

    Comment


    • #3
      Re: field level encryption?

      Thanks LittlePd

      Reading between the lines...........It sounds like you can encrypt the file's key fields and still process it with SETLL and Read.
      I hope so.

      Thanks Again
      GLS
      The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

      Comment


      • #4
        Re: field level encryption?

        I see this as like a database I/O exit point, where IBM is allowing access to the data base I/O stream for the purpose of encrypting/decrypting columns. The encryption/decryption happens outside of your program, so that you don't have to change anything. In other words, you do a write just like you've always done, but before the data gets to the table, the encryption "hook" takes over and your database column is encrypted. When you read, your results come from the database unencrypted, because the "hook" executed the decryption process.

        As far as key fields are concerned, I have no clue if you can encrypt those or not. I haven't gotten that deep into it yet. However, our LUG is having a presentation on 7.1 enhancements next Tuesday night. I'll let you know what I find out.
        "Time passes, but sometimes it beats the <crap> out of you as it goes."

        Comment


        • #5
          Re: field level encryption?

          Originally posted by littlepd View Post
          I'll let you know what I find out.
          I'd appreciate that.

          Thanks
          GLS
          The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

          Comment


          • #6
            Re: field level encryption?

            May be I could not follow correctly, but DB2 for i already has the ability to encrypt and decrypt database columns.
            There are several scalar functions ENCRYPT_RC2, ENCRYPT_TDES, ENCRYPT_AES and DECRYPT_BIT, DECRYPT_BINARY, DECRYPT_CHAR, DECRYPT_DB.

            For more information about Data(base) encryption you may check the following redbook:
            IBM System i Security:
            Protecting i5/OS Data with
            Encryption


            You may find a little more information about field leven encryption under release 7.1 in the following article:
            How Did IBM Enhance Security in 7.1?

            Birgitta
            Last edited by B.Hauser; April 17, 2010, 08:22 AM.

            Comment


            • #7
              Re: field level encryption?

              Hi Birgitta:

              The key to this thread is in this quote:
              No application changes required
              and this one:
              without changing the underlying application or any code.
              Using standard encryption/decryption methods each program which needs the encrypted data will need to be modified. These quotes suggest no modification required

              GLS
              Last edited by GLS400; April 19, 2010, 07:30 AM.
              The problem with quotes on the internet is that it is hard to verify their authenticity.....Abraham Lincoln

              Comment


              • #8
                Re: field level encryption?

                Did you read the second article?

                With field procedures the existing column values can be encrpyted. When inserting or updating a column with a field procedure, this procedure will be executed, the passed value encrypted and the encrypted value returned. This encrypted value will be shown when executing something like SELECT *, but for further use the field procedure will be called and the encrypted value deciphered for internal use. In this way you can add field procedures and encrypt your data without changing any of your programs because for internal use the dechiphered data is used. To get the decrypted/real value, the field procedure is needed. If someone will download your data (without the field procedure) the encrypted data will stay encrypted.

                Birgitta

                Comment

                Working...
                X