{
  "trx_id": "90f181ad2af88179b4917406601f609c8390e1a3",
  "block": 106149872,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-18T05:37:51",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "7115.469450 VESTS"
    }
  ]
}

{
  "trx_id": "0a8504c67e6faf24304c8a787bfb019670378bd2",
  "block": 106001873,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-05-13T01:41:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "4403.259045 VESTS"
    }
  ]
}

{
  "trx_id": "afc9809db85adf5708a17532a3f1a02f42e3c3ec",
  "block": 105517378,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-04-26T04:50:39",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "7127.985206 VESTS"
    }
  ]
}

{
  "trx_id": "7b68c9b6df2867fac97e195a238dcd465e64dbf9",
  "block": 102869146,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2026-01-23T22:16:15",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "4444.805864 VESTS"
    }
  ]
}

{
  "trx_id": "75c13ef2c62946ad171766e02e97b31354708aa9",
  "block": 91315372,
  "trx_in_block": 8,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2024-12-17T17:26:54",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "4609.025061 VESTS"
    }
  ]
}

{
  "trx_id": "c3375006929edd5afd7332b5e4e9dae50ff1651f",
  "block": 79869523,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-11-14T09:08:12",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "4778.158593 VESTS"
    }
  ]
}

{
  "trx_id": "8a199d163e68b53dc44ed652443b3f5629d7c390",
  "block": 78361938,
  "trx_in_block": 5,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2023-09-22T09:37:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "7715.067379 VESTS"
    }
  ]
}

{
  "trx_id": "e08784ee640d47fccadc3bf9cbf1dd3d186cb98d",
  "block": 69119796,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-11-03T17:10:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "7937.118817 VESTS"
    }
  ]
}

{
  "trx_id": "1d7dab533cf5d21e48efce0e331edfd28071a690",
  "block": 60823121,
  "trx_in_block": 18,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2022-01-17T22:26:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8157.226418 VESTS"
    }
  ]
}

{
  "trx_id": "3da05b80e0bb891bd1ea83d39c069de74a5ce308",
  "block": 54613484,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2021-06-14T05:39:00",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8341.420706 VESTS"
    }
  ]
}

{
  "trx_id": "86ad328883834c14e49ef0df202ea5de91543306",
  "block": 49360765,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-11T15:51:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8528.842680 VESTS"
    }
  ]
}

{
  "trx_id": "e2a5adf70df3318cd37c2f0f102fc1417b877130",
  "block": 49212294,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-06T09:27:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "1912.543513 VESTS"
    }
  ]
}

{
  "trx_id": "95b96afb85fcdb7596c24ec09bcbd9005cee14c8",
  "block": 49195853,
  "trx_in_block": 6,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-12-05T19:29:45",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8535.050534 VESTS"
    }
  ]
}

{
  "trx_id": "ce254c7c3d508b82bc8d0954099d78c8c274a59d",
  "block": 48269332,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-11-03T01:25:57",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "1920.017158 VESTS"
    }
  ]
}

{
  "trx_id": "2ca75a4c74601a8dc20297e54d0118d15f40cbc5",
  "block": 43222613,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-09T10:30:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8737.855893 VESTS"
    }
  ]
}

{
  "trx_id": "84843bdd2ba57e3632ec066f53971c54e053b40f",
  "block": 43199553,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-05-08T14:49:06",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "1953.311140 VESTS"
    }
  ]
}

{
  "trx_id": "fa494fd17cd75eb8027e0704d7200cdfe397b5d7",
  "block": 42568704,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2020-04-16T02:54:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8750.743341 VESTS"
    }
  ]
}

{
  "trx_id": "4b4391be3ef87507c28dd04f3b5c88e3122773b0",
  "block": 37547616,
  "trx_in_block": 3,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-10-23T22:57:54",
  "op": [
    "comment",
    {
      "parent_author": "remme",
      "parent_permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-remme-20191023t225753000z",
      "title": "",
      "body": "Congratulations @remme! You received a personal award!\n\n<table><tr><td>https://steemitimages.com/70x70/http://steemitboard.com/@remme/birthday2.png</td><td>Happy Birthday! - You are on the Steem blockchain for 2 years!</td></tr></table>\n\n<sub>_You can view [your badges on your Steem Board](https://steemitboard.com/@remme) and compare to others on the [Steem Ranking](https://steemitboard.com/ranking/index.php?name=remme)_</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\"><img src=\"https://steemitimages.com/64x128/https://files.steempeak.com/file/steempeak/arcange/YqQV5Tbj-image.png\"></a></td><td><a href=\"https://steemit.com/steemfest/@steemitboard/steemfest-commemorative-badge-refactored\">SteemFest⁴  commemorative badge refactored</a></td></tr></table>\n\n###### [Vote for @Steemitboard as a witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1) to get one more award and increased upvotes!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "efdc9101c923886e4c52ee6ffdbd809446d3b72c",
  "block": 32851632,
  "trx_in_block": 2,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2019-05-12T20:01:33",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "8946.360154 VESTS"
    }
  ]
}

{
  "trx_id": "e64da1ec2210a18ca31bd528868b48d210be1219",
  "block": 27085672,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-10-24T10:24:21",
  "op": [
    "comment",
    {
      "parent_author": "remme",
      "parent_permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "author": "steemitboard",
      "permlink": "steemitboard-notify-remme-20181024t102420000z",
      "title": "",
      "body": "Congratulations @remme! You have received a personal award!\n\n[![](https://steemitimages.com/70x70/http://steemitboard.com/@remme/birthday1.png)](http://steemitboard.com/@remme)  1 Year on Steemit\n<sub>_Click on the badge to view your Board of Honor._</sub>\n\n\n**Do not miss the last post from @steemitboard:**\n<table><tr><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\"><img src=\"https://steemitimages.com/64x128/https://cdn.steemitimages.com/DQmfRVpHQhLDhnjDtqck8GPv9NPvNKPfMsDaAFDE1D9Er2Z/header_ranking.png\"></a></td><td><a href=\"https://steemit.com/steemitboard/@steemitboard/steemitboard-ranking-update-resteem-and-resteemed-added\">SteemitBoard Ranking update - Resteem and Resteemed added</a></td></tr></table>\n\n> Support [SteemitBoard's project](https://steemit.com/@steemitboard)! **[Vote for its witness](https://v2.steemconnect.com/sign/account-witness-vote?witness=steemitboard&approve=1)** and **get one more award**!",
      "json_metadata": "{\"image\":[\"https://steemitboard.com/img/notify.png\"]}"
    }
  ]
}

{
  "trx_id": "4400f92bf6e79432502f4d4e28a61d5cabf3348b",
  "block": 22494249,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-05-16T23:57:24",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "9145.971022 VESTS"
    }
  ]
}

{
  "trx_id": "37e26ce08ce71363fe5b5aae03bb4423fc193b12",
  "block": 21771314,
  "trx_in_block": 31,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-04-21T20:51:18",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "29533.977592 VESTS"
    }
  ]
}

{
  "trx_id": "a077a0f950ccf2dc8592b26148cc1e055cd6e105",
  "block": 19850413,
  "trx_in_block": 33,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-14T02:32:27",
  "op": [
    "vote",
    {
      "voter": "cryptoball",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "51abbae1affb7968278b86f879be7bc9a3cfea83",
  "block": 19734567,
  "trx_in_block": 67,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-10T01:55:45",
  "op": [
    "vote",
    {
      "voter": "vavan19",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "4891765a09b5322ed7d57ccd3c42b4a2c271077c",
  "block": 19679780,
  "trx_in_block": 38,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-08T04:08:18",
  "op": [
    "vote",
    {
      "voter": "voski",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "532bbf9c7426f90eed5fbb030c5e4b4c0ca3fa6c",
  "block": 19679777,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-02-08T04:08:09",
  "op": [
    "vote",
    {
      "voter": "voski",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "2aaeff6984a3955ec2c10ce15653d3976de3b042",
  "block": 19277920,
  "trx_in_block": 40,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-01-25T04:49:48",
  "op": [
    "vote",
    {
      "voter": "jlanzago",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "d0996a9c081202eea77517f8f845d5df0a4c9377",
  "block": 19277919,
  "trx_in_block": 42,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-01-25T04:49:45",
  "op": [
    "vote",
    {
      "voter": "jlanzago",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "60eeecb60823421237a6015df1a770289ac2eaab",
  "block": 19035932,
  "trx_in_block": 4,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2018-01-16T19:05:18",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "dmae",
      "permlink": "mazok4qv",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "181c4c708f46d726465b6dc5b4a27b13094a2821",
  "block": 18032646,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-12-12T22:23:09",
  "op": [
    "delegate_vesting_shares",
    {
      "delegator": "steem",
      "delegatee": "remme",
      "vesting_shares": "29737.809644 VESTS"
    }
  ]
}

{
  "trx_id": "f84a07abf7b3c85f0e6f0964a99f7e99824147b3",
  "block": 17938055,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-12-09T15:32:18",
  "op": [
    "vote",
    {
      "voter": "ogonnanwasike",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "ff233b2e058d1ad7a226b8c6ff91b426d78a818c",
  "block": 17938049,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-12-09T15:32:00",
  "op": [
    "vote",
    {
      "voter": "ogonnanwasike",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "a90b89106c688c155ce07188b9fc7acdd8785c90",
  "block": 17233735,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-15T04:20:03",
  "op": [
    "vote",
    {
      "voter": "poh",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "e2d8ed8d83b48aba604a5cc1bb21c441bd86a177",
  "block": 17058913,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-11-09T02:35:27",
  "op": [
    "vote",
    {
      "voter": "pandoraboxchain",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "00ad385017f7c87ef414d5033c011e6da8c22bc1",
  "block": 16821623,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:43:27",
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "0c85eab35161838480f41894767275610ea4b7f2",
  "block": 16821433,
  "trx_in_block": 45,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:33:57",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"deanero\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "46f64f976d9df9f2b043d30d2f97ddeb769e6865",
  "block": 16821315,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:28:03",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"taas\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "3231637d99fc6ed56368c7f1d2ffbec774b0357a",
  "block": 16821191,
  "trx_in_block": 19,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:21:51",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"dana-edwards\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "813cdc58ed9980cca5d6274fd1bee866300b1249",
  "block": 16821123,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:18:27",
  "op": [
    "account_update",
    {
      "account": "remme",
      "memo_key": "STM853edGKiFqQuyX6WcpYSGHyC3oZpitDFyGynh72bhKtV3vWT9a",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/717825820845285376/E4IvF1YM_400x400.jpg\",\"location\":\"Blockchain\",\"name\":\"REMME\",\"about\":\"Distributed authentication for humans and devices. Powered by Blockchain.\",\"website\":\"https://www.remme.io\"}}"
    }
  ]
}

{
  "trx_id": "6a2181491d76a99be0044193b254e1e1d08468e8",
  "block": 16821067,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-31T20:15:39",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "cybersecurity",
      "author": "remme",
      "permlink": "how-remme-protects-against-phishing-dictionary-and-brute-force-pharming-ddos-and-other-types-of-malicious-attacks",
      "title": "How REMME protects against Phishing, Dictionary & brute-force, Pharming, DDoS and other types of malicious attacks",
      "body": "![Attacks.png](https://steemitimages.com/DQmVxy6mdT2TpC2ZGTRYrr287gfPZFmRgGvuVxfdpv2pMjP/Attacks.png)\n\nFollowing the rapid expansion of online connectivity, information security is of the highest demand nowadays. Internet network has evolved far beyond the mere exchange of information, connecting various aspects of our daily lives and being present even in fridges and cars. IoT, Big Data, ubiquitous handheld devices of all shapes — all this makes us carefully consider how to protect data on its way through all connected channels, either those of a service provider or a common user.\n\n**REMME acts on various architectural levels (based on [OSI Multilevel Architecture](https://en.wikipedia.org/wiki/OSI_model)):**\n* Physical level\n* Data link level\n* Network level\n* Transportation level\n* Session level\n* Presentation level\n* Application level\n\nNow, let’s see how our solution can protect users and companies against various types of attacks.\n\n## DDoS ##\nThere are two types of DDoS attacks: low-level (SYN-flooding), and high-level (multiple requests to the application, e.g. multiple GET requests to the web server). Low-level attacks are processed at the data link level, while high-level — at the application level. REMME and SSL may limit the access to the application level on both the channel (IPSec) or transportation (TLS) levels.\n\n## Hardware Trojan ## \nIn this case, REMME offers an indirect protection from the malicious hardware that works through its physical form. If a common USB Disk is used as a keylogger, REMME may mitigate data losses, as the user won’t need to type passwords. A digital certificate can also be provided for all pluggable USB devices (this feature will be implemented in the upcoming version of REMME).\n\n## MiM (Man-in-the-middle) attack ## \ncryptanalyzes and modifies victim’s data, by inserting another system on its way. There are multiple ways to perform such attack, e.g., ARP-spoofing, attacks on BGP routers, DNS server response substitution etc. To access the network traffic, it’s sufficient to change the internet provider’s BGP. You don’t even need to hack the router, as BGP doesn’t offer cryptographic authentication of the data exchange between the partners running a network segment. REMME encryption technologies eliminate data wiretapping or substitution, as standard protocols with unsafe channels switch over to encrypted ones (e.g. HTTP Strict-Transport-Security protocol, that makes browser always use HTTPS). While it is impossible to fend off MiM attacks in a standard hierarchical scheme of certificates (when an attacker has access to the certification body), REMME provides such protection, as attackers won’t be able to create fake certificates on behalf of the owner in a decentralized blockchain-based system.\n\n## Pharming ## \nredirects the user to the false IP-address. By using fake DNS response, it is easy to frame a user, making him vulnerable to further phishing or MiM attacks. REMME technology can recognize if the system you want to connect with has a wrong signature.\n\n## XSS (Cross-Site Scripting) ## \nadds an external script to the website, operating with the web page data, e.g. copying and sending data to the server. REMME can’t directly influence this process, but can minimize the damage from such attack as all data used for authentication is stored within a protected repository of system keys. Thus, scripts from the web page won’t receive access to this data, and all suspicious activities have to be confirmed through 2FA.\n\n## Malicious browser add-ons ## \nBrowser add-ons are very common these days, however, not all extensions may be useful. As extensions have access to the browser’s data sent both from the server and a client (via the data forms), malicious add-ons may intercept any sensitive information, including passwords and website session identifiers (cookies). A fresh example: in 2017, at least 37.000 users were tricked into downloading a fake AdBlock add-on for Google Chrome. Previously, in 2016 a student from Denmark discovered a set of Google Chrome malicious add-ons, hijacking Facebook accounts. REMME can help protect your data in such cases, as it uses SSL certificates for user authentication, kept in a specialized insulating storage. Thus, it’s impossible to reach protected SSL certificates via browser plugins or add-ons. In order to receive access to this storage, the attacker has to gain access to the whole system. Even in this case, the certificate will be protected with a key phrase, giving users additional time to recall the certificate.\n\n## Dictionary and brute-force attacks ## \nThese types of atacks are based on password mining. With asymmetrical cryptography, this type of attack has a close to zero chance of success, while requiring a tone of resources and efforts from hackers.\n\n## Password reuse attack ## \nIt is impossible with asymmetrical cryptography in place, as the Diffie-Hellman algorithm is used for identification with certificates and keys exchange, successfully eliminating the possibility of such attack.\n\n## Phishing ## \nA targeted email attack, exploiting the human factor and using elements of social engineering. Phishing is commonly conducted through emails, sent to the recipient from a familiar person or service while containing malware or links to seemingly legitimate compromised websites. REMME S/MIME technology allows signing emails with a private key, adding an x.509 certificate with a public key in the message. Thus, it is easy to check the resource of the message that helps to define the level of trust, while revealing and blocking the virus source.\n\n## Evil twin ## \nIt’s a specific type of phishing attack in wireless networks. A hacker creates a copy of wireless entry point within a radius of user signal and substitutes the original entry point with its clone, redirecting all traffic of a victim. To protect the data from this type of attack, REMME suggests using WPA2-Enterprise encryption with EAP authorization in all wireless networks. This scheme can utilize Radius server with REMME solution, while the latter would require some tuning of its settings.\n\n-----\n**Learn More**\nTo learn more about the [REMME](https://www.remme.io) project check out our white paper and subscribe for email updates. Follow us on [Twitter](https://twitter.com/remme_io), and join our growing community in [Telegram](https://twitter.com/remme_io).",
      "json_metadata": "{\"tags\":[\"cybersecurity\",\"blockchain\",\"technology\",\"remme\",\"hacker\"],\"image\":[\"https://steemitimages.com/DQmVxy6mdT2TpC2ZGTRYrr287gfPZFmRgGvuVxfdpv2pMjP/Attacks.png\"],\"links\":[\"https://en.wikipedia.org/wiki/OSI_model\",\"https://www.remme.io\",\"https://twitter.com/remme_io\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "696a8e927bd8cf237a9a46fa562f08820d6b3b4f",
  "block": 16782031,
  "trx_in_block": 0,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-30T11:43:45",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"cryptoriddler\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "23854247933cad8bccf951185364d24860aeaff7",
  "block": 16762516,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:27:48",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"elliotmeijer\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "5833fb5ff9f800697e05f4c0b73a86c85a2fbe5b",
  "block": 16762272,
  "trx_in_block": 20,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:15:36",
  "op": [
    "vote",
    {
      "voter": "fivestargroup",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 2
    }
  ]
}

{
  "trx_id": "6f12e0f91ec1e42e302012daa4df5f8c1b08f98d",
  "block": 16762271,
  "trx_in_block": 32,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:15:33",
  "op": [
    "vote",
    {
      "voter": "primetimesports",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 2
    }
  ]
}

{
  "trx_id": "09531c161b1da2a0ed7df8611946402aafb56c81",
  "block": 16762248,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:14:24",
  "op": [
    "vote",
    {
      "voter": "mamont",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "62ea632cf39b1988bf1c4044a1559f7fd73c72b1",
  "block": 16762192,
  "trx_in_block": 7,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:11:36",
  "op": [
    "vote",
    {
      "voter": "jrai",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "dc045b06a504411298a8478f9ade6653d2c7fccc",
  "block": 16762077,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:05:51",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "title": "REMME: using blockchain for Access Management and distributed authentication",
      "body": "![medium_iam_cover.png](https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png)\n\n**Good security is like good health: you don’t truly appreciate it till it’s gone.**\n\nIn our day-to-day lives, passwords, account access and authentication aren’t remotely fun, glamorous or profitable; they’re a nuisance that we endure because it’s been drummed into us that the alternative is far worse.\n\nThe horror stories aren’t apocryphal either — sadly they’re all too real. The cost of a major systems breach can be astronomical, not only from a financial perspective, but also from a moral one. No one wants to be remembered as “that company that got hacked” or “that gobby corporation whose spools were picked apart in the gossip mags”. Don’t be like Equifax or Sony or any one of the countless other companies that are breached every year.\n\nThe trouble is, even if you do everything by the book — even if you use strong passwords and restrict access and follow all the other best practices that have been inculcated in us over the years — it still might not be enough. All it takes is for one hapless employee to open an email attachment they shouldn’t, or one infected thumb drive to be plugged into the network and — boom — years of diligent behaviour are erased in a trice.\n\n\n## Taking aim at IAM\nBut enough with the scare stories. We’re not here to paint doomsday scenarios (not today anyway). We actually want to discuss access management. It’s a benign name for a critical business process, incorporating username and password control for your entire organization. Every company, regardless of size, has some degree of hierarchy when it comes to system access. After all, you don’t give your intern the same level of access as your CEO. Access management isn’t just about decreeing who can see what — it’s also about implementing a robust framework that will deter unauthorized entities. Your access management system is only as strong as its weakest link however.\n\nWhile some businesses view access management as little more than a distraction or an annoyance, here at [REMME](https://www.remme.io) we have a different approach. That’s because developing access management solutions is what we do. Or to put it differently, securing your business is our business. Although we’re big fans of access management, it’s no secret that we’re not fond of the current paradigm. That’s why we went to the trouble of building a radically different solution using the security provided by the blockchain.\n\n\n## Certification without the centralization\n\nClassical certificate management structures operate on a hierarchical basis, all overseen by a centralized certificate authority. This is how it’s always been done, and it’s probably how it would have continued to be done were it not for the rise of blockchain technology. We’re not the first company to stumble upon blockchain’s potential for enhancing security and granting systems access; other companies have already trialled identity-based solutions, with Civic and Uport notable examples.\n\nThese systems are great for resolving issues of identity, but they’re not designed to control issues of access. In other words, even if you are who you say you are, should you be accessing these files? Determining this calls for a new system of certificate management. We could achieve this by storing certificate data on the blockchain, but in our opinion this approach is less than ideal. Instead, we’ve created a means of saving and revoking certificates that utilizes a secret message that’s signed by a private key associated with that particular blockchain address.\n\nThis results in an elegant system that is blockchain agnostic. Pick a blockchain — Bitcoin; Emercoin; Ethereum — or even a sidechain such as Rootstock or Exonum and we’ll set up a certificate solution to suit. We allow for self-signed certificates, ones signed by our own certifying center or ones signed by an official third party. X.509 certificates have long been the defining standard for public key certificates. REMME takes that framework and builds a [distributed Public Key Infrastructure](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) on top of it, essentially repurposing SSL/TLS and preventing the entire channel from attack.\n\nX.509 certificates is another topic for another time: we’ll spare you from the minutiae for now. For the purposes of this article, we just want to finish by touching upon how the certification revocation process works. This is achieved by publishing a secret revocation message that is signed using a private key. There’s no need to wait for blockchain confirmation as the certificate is valid immediately. To further bolster security, our clients can also activate two-factor authentication. That way, even if a private SSL certificate is somehow compromised, there’s an added layer of security to contend with.\n\n<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\" frameborder=\"0\" allowfullscreen></iframe>\n\n‘Decentralization’ (like ‘blockchain’) is one of those words that gets touted about a lot, including cases where it’s not really needed. When it comes to access management however, we firmly believe that the distributed system we’ve created is one that is stronger, more transparent and more secure thanks to a destributed model which means there is no single point of failure. The name REMME is a truncation of “remember me”. If you value the security of your organization, it’s a name you’ll want to recall. As the second phase of our [pilot program](https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912) rolls out later this year, expect to be hearing a lot more about REMME and our innovative new IAM framework.\n\n**Access management doesn’t have to be exciting — it just has to be secure.** Here at REMME, we’re pretty confident we’ve got that latter requisite locked down.\n\n------------------\n\n**Learn More**\nTo learn more about the REMME project check out our [white paper](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) and subscribe for [email updates](https://www.remme.io). Follow us on [Twitter](https://twitter.com/remme_io), and join our growing community in [Telegram](https://t.me/remme).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"cybersecurity\",\"authentication\",\"technology\",\"remme\"],\"image\":[\"https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png\",\"https://img.youtube.com/vi/9APHeHRmrGw/0.jpg\"],\"links\":[\"https://www.remme.io\",\"https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view\",\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\",\"https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912\",\"https://twitter.com/remme_io\",\"https://t.me/remme\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "928fc801e27bfe1488cc910cda1a4d2935966b84",
  "block": 16762044,
  "trx_in_block": 25,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:04:12",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "permlink": "keep-your-information-safe-with-blockchain-technology",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "8c1002af786077b70368af6e97988d04bc5a550c",
  "block": 16762041,
  "trx_in_block": 1,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:04:03",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "permlink": "the-hackathon-we-won",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "2c798b8784be170c172d34a04c45eed2cfed9849",
  "block": 16762034,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:03:42",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "garrettjgrubbs",
      "permlink": "how-blockchain-can-make-passwords-obsolete",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "117eae17a4ddf08166c79bb2607708383ff198de",
  "block": 16762032,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:03:36",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"garrettjgrubbs\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "66baadccee5177e3e940a934a9d9db78711ad109",
  "block": 16762012,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:02:36",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "permlink": "remme-technical-white-paper",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "9687d25c06cf403d7b56b70c340d24fb1a9cc62d",
  "block": 16761996,
  "trx_in_block": 24,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:01:48",
  "op": [
    "vote",
    {
      "voter": "remme",
      "author": "mamont",
      "permlink": "hi-steem-my-name-is-alex-momot-i-m-from-kiev-ukraine",
      "weight": 10000
    }
  ]
}

{
  "trx_id": "dbf9437dd8adf2d43c573267c038f35eb11e0a44",
  "block": 16761989,
  "trx_in_block": 16,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T19:01:27",
  "op": [
    "custom_json",
    {
      "required_auths": [],
      "required_posting_auths": [
        "remme"
      ],
      "id": "follow",
      "json": "[\"follow\",{\"follower\":\"remme\",\"following\":\"mamont\",\"what\":[\"blog\"]}]"
    }
  ]
}

{
  "trx_id": "1965e8f4377938254e402f48289a9065ffce1734",
  "block": 16761922,
  "trx_in_block": 15,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T18:58:06",
  "op": [
    "delete_comment",
    {
      "author": "remme",
      "permlink": "2cfxyk-remme-using-blockchain-for-access-management-and-distributed-authentication"
    }
  ]
}

{
  "trx_id": "7df34f879ac2ca4f8c491b9002029ca56e4a2cf5",
  "block": 16761854,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T18:54:42",
  "op": [
    "comment_options",
    {
      "author": "remme",
      "permlink": "2cfxyk-remme-using-blockchain-for-access-management-and-distributed-authentication",
      "max_accepted_payout": "0.000 SBD",
      "percent_steem_dollars": 10000,
      "allow_votes": true,
      "allow_curation_rewards": true,
      "extensions": []
    }
  ]
}

{
  "trx_id": "7df34f879ac2ca4f8c491b9002029ca56e4a2cf5",
  "block": 16761854,
  "trx_in_block": 22,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T18:54:42",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "remme",
      "permlink": "2cfxyk-remme-using-blockchain-for-access-management-and-distributed-authentication",
      "title": "REMME: using blockchain for Access Management and distributed authentication",
      "body": "![medium_iam_cover.png](https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png)\n\n**Good security is like good health: you don’t truly appreciate it till it’s gone.**\n\nIn our day-to-day lives, passwords, account access and authentication aren’t remotely fun, glamorous or profitable; they’re a nuisance that we endure because it’s been drummed into us that the alternative is far worse.\n\nThe horror stories aren’t apocryphal either — sadly they’re all too real. The cost of a major systems breach can be astronomical, not only from a financial perspective, but also from a moral one. No one wants to be remembered as “that company that got hacked” or “that gobby corporation whose spools were picked apart in the gossip mags”. Don’t be like Equifax or Sony or any one of the countless other companies that are breached every year.\n\nThe trouble is, even if you do everything by the book — even if you use strong passwords and restrict access and follow all the other best practices that have been inculcated in us over the years — it still might not be enough. All it takes is for one hapless employee to open an email attachment they shouldn’t, or one infected thumb drive to be plugged into the network and — boom — years of diligent behaviour are erased in a trice.\n\n\n## Taking aim at IAM\nBut enough with the scare stories. We’re not here to paint doomsday scenarios (not today anyway). We actually want to discuss access management. It’s a benign name for a critical business process, incorporating username and password control for your entire organization. Every company, regardless of size, has some degree of hierarchy when it comes to system access. After all, you don’t give your intern the same level of access as your CEO. Access management isn’t just about decreeing who can see what — it’s also about implementing a robust framework that will deter unauthorized entities. Your access management system is only as strong as its weakest link however.\n\nWhile some businesses view access management as little more than a distraction or an annoyance, here at [REMME](https://www.remme.io) we have a different approach. That’s because developing access management solutions is what we do. Or to put it differently, securing your business is our business. Although we’re big fans of access management, it’s no secret that we’re not fond of the current paradigm. That’s why we went to the trouble of building a radically different solution using the security provided by the blockchain.\n\n\n## Certification without the centralization\n\nClassical certificate management structures operate on a hierarchical basis, all overseen by a centralized certificate authority. This is how it’s always been done, and it’s probably how it would have continued to be done were it not for the rise of blockchain technology. We’re not the first company to stumble upon blockchain’s potential for enhancing security and granting systems access; other companies have already trialled identity-based solutions, with Civic and Uport notable examples.\n\nThese systems are great for resolving issues of identity, but they’re not designed to control issues of access. In other words, even if you are who you say you are, should you be accessing these files? Determining this calls for a new system of certificate management. We could achieve this by storing certificate data on the blockchain, but in our opinion this approach is less than ideal. Instead, we’ve created a means of saving and revoking certificates that utilizes a secret message that’s signed by a private key associated with that particular blockchain address.\n\nThis results in an elegant system that is blockchain agnostic. Pick a blockchain — Bitcoin; Emercoin; Ethereum — or even a sidechain such as Rootstock or Exonum and we’ll set up a certificate solution to suit. We allow for self-signed certificates, ones signed by our own certifying center or ones signed by an official third party. X.509 certificates have long been the defining standard for public key certificates. REMME takes that framework and builds a [distributed Public Key Infrastructure](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) on top of it, essentially repurposing SSL/TLS and preventing the entire channel from attack.\n\nX.509 certificates is another topic for another time: we’ll spare you from the minutiae for now. For the purposes of this article, we just want to finish by touching upon how the certification revocation process works. This is achieved by publishing a secret revocation message that is signed using a private key. There’s no need to wait for blockchain confirmation as the certificate is valid immediately. To further bolster security, our clients can also activate two-factor authentication. That way, even if a private SSL certificate is somehow compromised, there’s an added layer of security to contend with.\n\n<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\" frameborder=\"0\" allowfullscreen></iframe>\n\n‘Decentralization’ (like ‘blockchain’) is one of those words that gets touted about a lot, including cases where it’s not really needed. When it comes to access management however, we firmly believe that the distributed system we’ve created is one that is stronger, more transparent and more secure thanks to a destributed model which means there is no single point of failure. The name REMME is a truncation of “remember me”. If you value the security of your organization, it’s a name you’ll want to recall. As the second phase of our [pilot program](https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912) rolls out later this year, expect to be hearing a lot more about REMME and our innovative new IAM framework.\n\n**Access management doesn’t have to be exciting — it just has to be secure.** Here at REMME, we’re pretty confident we’ve got that latter requisite locked down.\n\n------------------\n\n**Learn More**\nTo learn more about the REMME project check out our [white paper](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) and subscribe for [email updates](https://www.remme.io). Follow us on [Twitter](https://twitter.com/remme_io), and join our growing community in [Telegram](https://t.me/remme).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"cybersecurity\",\"crypto\",\"technology\",\"blog\"],\"image\":[\"https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png\",\"https://img.youtube.com/vi/9APHeHRmrGw/0.jpg\"],\"links\":[\"https://www.remme.io\",\"https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view\",\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\",\"https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912\",\"https://twitter.com/remme_io\",\"https://t.me/remme\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "9c7655ce366f48e8354c48aaf5200f39192230b5",
  "block": 16761731,
  "trx_in_block": 9,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-29T18:48:33",
  "op": [
    "comment",
    {
      "parent_author": "",
      "parent_permlink": "blockchain",
      "author": "remme",
      "permlink": "remme-using-blockchain-for-access-management-and-distributed-authentication",
      "title": "REMME: using blockchain for Access Management and distributed authentication",
      "body": "![medium_iam_cover.png](https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png)\n\n**Good security is like good health: you don’t truly appreciate it till it’s gone.**\n\nIn our day-to-day lives, passwords, account access and authentication aren’t remotely fun, glamorous or profitable; they’re a nuisance that we endure because it’s been drummed into us that the alternative is far worse.\n\nThe horror stories aren’t apocryphal either — sadly they’re all too real. The cost of a major systems breach can be astronomical, not only from a financial perspective, but also from a moral one. No one wants to be remembered as “that company that got hacked” or “that gobby corporation whose spools were picked apart in the gossip mags”. Don’t be like Equifax or Sony or any one of the countless other companies that are breached every year.\n\nThe trouble is, even if you do everything by the book — even if you use strong passwords and restrict access and follow all the other best practices that have been inculcated in us over the years — it still might not be enough. All it takes is for one hapless employee to open an email attachment they shouldn’t, or one infected thumb drive to be plugged into the network and — boom — years of diligent behaviour are erased in a trice.\n\n\n## Taking aim at IAM\nBut enough with the scare stories. We’re not here to paint doomsday scenarios (not today anyway). We actually want to discuss access management. It’s a benign name for a critical business process, incorporating username and password control for your entire organization. Every company, regardless of size, has some degree of hierarchy when it comes to system access. After all, you don’t give your intern the same level of access as your CEO. Access management isn’t just about decreeing who can see what — it’s also about implementing a robust framework that will deter unauthorized entities. Your access management system is only as strong as its weakest link however.\n\nWhile some businesses view access management as little more than a distraction or an annoyance, here at [REMME](https://www.remme.io) we have a different approach. That’s because developing access management solutions is what we do. Or to put it differently, securing your business is our business. Although we’re big fans of access management, it’s no secret that we’re not fond of the current paradigm. That’s why we went to the trouble of building a radically different solution using the security provided by the blockchain.\n\n\n## Certification without the centralization\n\nClassical certificate management structures operate on a hierarchical basis, all overseen by a centralized certificate authority. This is how it’s always been done, and it’s probably how it would have continued to be done were it not for the rise of blockchain technology. We’re not the first company to stumble upon blockchain’s potential for enhancing security and granting systems access; other companies have already trialled identity-based solutions, with Civic and Uport notable examples.\n\nThese systems are great for resolving issues of identity, but they’re not designed to control issues of access. In other words, even if you are who you say you are, should you be accessing these files? Determining this calls for a new system of certificate management. We could achieve this by storing certificate data on the blockchain, but in our opinion this approach is less than ideal. Instead, we’ve created a means of saving and revoking certificates that utilizes a secret message that’s signed by a private key associated with that particular blockchain address.\n\nThis results in an elegant system that is blockchain agnostic. Pick a blockchain — Bitcoin; Emercoin; Ethereum — or even a sidechain such as Rootstock or Exonum and we’ll set up a certificate solution to suit. We allow for self-signed certificates, ones signed by our own certifying center or ones signed by an official third party. X.509 certificates have long been the defining standard for public key certificates. REMME takes that framework and builds a [distributed Public Key Infrastructure](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) on top of it, essentially repurposing SSL/TLS and preventing the entire channel from attack.\n\nX.509 certificates is another topic for another time: we’ll spare you from the minutiae for now. For the purposes of this article, we just want to finish by touching upon how the certification revocation process works. This is achieved by publishing a secret revocation message that is signed using a private key. There’s no need to wait for blockchain confirmation as the certificate is valid immediately. To further bolster security, our clients can also activate two-factor authentication. That way, even if a private SSL certificate is somehow compromised, there’s an added layer of security to contend with.\n\n<iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\" frameborder=\"0\" allowfullscreen></iframe>\n\n‘Decentralization’ (like ‘blockchain’) is one of those words that gets touted about a lot, including cases where it’s not really needed. When it comes to access management however, we firmly believe that the distributed system we’ve created is one that is stronger, more transparent and more secure thanks to a destributed model which means there is no single point of failure. The name REMME is a truncation of “remember me”. If you value the security of your organization, it’s a name you’ll want to recall. As the second phase of our [pilot program](https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912) rolls out later this year, expect to be hearing a lot more about REMME and our innovative new IAM framework.\n\n**Access management doesn’t have to be exciting — it just has to be secure.** Here at REMME, we’re pretty confident we’ve got that latter requisite locked down.\n\n------------------\n\n**Learn More**\nTo learn more about the REMME project check out our [white paper](https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view) and subscribe for [email updates](https://www.remme.io). Follow us on [Twitter](https://twitter.com/remme_io), and join our growing community in [Telegram](https://t.me/remme).",
      "json_metadata": "{\"tags\":[\"blockchain\",\"cybersecurity\",\"crypto\",\"technology\",\"blog\"],\"image\":[\"https://steemitimages.com/DQmPNfK2qEeX7TJC3e1kbZ2EbqDhChGjN89STcbivFyzejC/medium_iam_cover.png\",\"https://img.youtube.com/vi/9APHeHRmrGw/0.jpg\"],\"links\":[\"https://www.remme.io\",\"https://drive.google.com/file/d/0B1jTRGmj_3khUV9RTERnYzNvaE0/view\",\"https://www.youtube.com/embed/9APHeHRmrGw?rel=0\",\"https://medium.com/remme/remmes-2018-pilot-program-is-ready-to-launch-3165380c1912\",\"https://twitter.com/remme_io\",\"https://t.me/remme\"],\"app\":\"steemit/0.1\",\"format\":\"markdown\"}"
    }
  ]
}

{
  "trx_id": "e4516a05028145598202795228ee1bc07b93c00a",
  "block": 16591991,
  "trx_in_block": 17,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-23T21:16:06",
  "op": [
    "account_update",
    {
      "account": "remme",
      "memo_key": "STM853edGKiFqQuyX6WcpYSGHyC3oZpitDFyGynh72bhKtV3vWT9a",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://pbs.twimg.com/profile_images/717825820845285376/E4IvF1YM_400x400.jpg\",\"location\":\"Blockchain\"}}"
    }
  ]
}

{
  "trx_id": "4c31634000d0302005a71eae8686d3c4e066b08b",
  "block": 16591920,
  "trx_in_block": 10,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-23T21:12:33",
  "op": [
    "account_update",
    {
      "account": "remme",
      "memo_key": "STM853edGKiFqQuyX6WcpYSGHyC3oZpitDFyGynh72bhKtV3vWT9a",
      "json_metadata": "{\"profile\":{\"profile_image\":\"https://www.facebook.com/1167456903266942/photos/1167492296596736/\"}}"
    }
  ]
}

{
  "trx_id": "8e4f91b5d1b9842df18670aab67ee92e0246b80e",
  "block": 16591824,
  "trx_in_block": 13,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-23T21:07:45",
  "op": [
    "account_update",
    {
      "account": "remme",
      "memo_key": "STM853edGKiFqQuyX6WcpYSGHyC3oZpitDFyGynh72bhKtV3vWT9a",
      "json_metadata": "{\"profile\":{\"website\":\"https://www.remme.io/\"}}"
    }
  ]
}

{
  "trx_id": "5715cbb5af635ad8bb04e5566b0f1c477c6a1a30",
  "block": 16591778,
  "trx_in_block": 11,
  "op_in_trx": 0,
  "virtual_op": 0,
  "timestamp": "2017-10-23T21:05:27",
  "op": [
    "account_create_with_delegation",
    {
      "fee": "0.500 STEEM",
      "delegation": "57000.000000 VESTS",
      "creator": "steem",
      "new_account_name": "remme",
      "owner": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM5oK6GuG8gyQunR7v3mpi6xTc3CUC2kSHokZSENhnyXuXYpycEP",
            1
          ]
        ]
      },
      "active": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM6zojNCWRAFR3tsGQei6LhuRuqm22HWM73bePmx6uA1jAYiWAE9",
            1
          ]
        ]
      },
      "posting": {
        "weight_threshold": 1,
        "account_auths": [],
        "key_auths": [
          [
            "STM6R7AMNsPqXW6y31sNrFuVjy8sw3XZ6Gp3y37wzzLeE3MkUnGqC",
            1
          ]
        ]
      },
      "memo_key": "STM853edGKiFqQuyX6WcpYSGHyC3oZpitDFyGynh72bhKtV3vWT9a",
      "json_metadata": "",
      "extensions": []
    }
  ]
}