Architected Futures™

Tools and strategies ... for boiling the ocean

EATS Security

<Doing>

https://docs.woocommerce.com/document/ssl-and-https/

<TODO>

[Fix this. There is a real security scheme here, and about 25 other things with various degrees of relativity. This needs demultiplexing, a lot! Especially that big block in the middle. It is only "published" so that, I hope, I don't have links to things that are "hidden" from view. That would break my whole point about "open." Normally, this should get cleaned up in an editorial review before being "posted" or "published" just to keep the site readable by "normal" people. That publication review process is in a BCC presentation that should be made available in the files section. Some of this is a little weird to read, but at least it's not as bad as my post-it note collection. :) ]

Integrate as a SAC book entry.

Publish security documentation from BCC class.

Security Model = RBAC diagram and related "process" maps.

Encryption scheme is hierarchical encryption based on user option.

  1. Member selected scheme from GUID list defines algorithm, which they can also supply to be implanted as a "user extension" (GUID will be generated for identification purposes and flow management.)
  2. Member supplies "self encryption" one-way encryption key for member's own identity. Member is identified by GUID.
  3. Member selected scheme from (1) is used within the EATS security process generation management scheme to identify multiplexing/demultiplexing procedures for information management.
  4. Member identity is used within member authorized contexts to establish authorizations for content and process access management.

For now. Hopefully this works for "secrecy" assurance on private and proprietary content and facilities. In pseudo English:

  1. In EATS, the content subsystem uses a GUID as an identifier. (See font page, column 3, near/at the bottom.) For everything. Soup, kitchen, nuts, bolts, aircraft, the Panet(?) Pluto, and every member of the community.
  2. We catalog it. We care about stuff, we catalog it. We don't care about stuff, we don't catalog it. But we don't assign community GUIDs until we hear from you. We don't assign any GUIDs until we identify something. And then we assign a GUID if its something we didn't already know.  And we start to classify it. (If we've never seen you/it before, and never heard of you: "Oh, you're a new member" or "Oh, that's a new idea!", we give out new GUIDs. If we've heard about you before you arrive, there might already be a GUID waiting in your name.) Community member GUIDs are no different from any other GUID. They consist of a lot of mathematics gibberish that is used to try to assure that they are unique in the universe, yes, that one, at least that's the idea. So, every thing and every one has a unique identifier. But, at the same time, "they are all the same" so there is no way you can just look at one and tell what it's about, if it's a "who" or a "what" or a "where" or a "how" or a "when" or a "why." Whether it's an object or an action. Whether its a noun or a verb. Just that it's something that we have identified, and it's in our model. So, like everything else, you get lost in the system. Big deal, you've got a tag. It helps you get free badges. But you have to work for them. They need to be earned. Except for the one that says "member." That's free, or so they say. [Warning normal people, weird or geek science ahead --> happens at these1-> [The reason for the extra stuff above is because this works both ways. Not the security, the tagging. That same tagging that "gets things lost" is the mechanism for putting them back together, for "un-losing" them." Multiplexing and demultiplexing. [And "weaving", aka creating new patterns, aka intelligence [Freelinking: node title “Intelligent Un-losing + pattern matching + recognition would be the next frontier[]Anyone there yet? That sounds like security in the movies, how the cops track and spot the guy instantly by knowing his patterns and doing facial recognition on the monitor as he goes through the subway. So a frontier must be further out.” does not exist] EATS at its current design level is about pattern matched multiplexing as an Augmented Intelligence Toolkit. This is core to how it's done.[Core Architecture Concept]] That other stuff in there, those were maybes. This is how I do "architecture." It's how I also bias my algorithms. By asking, what would my next moves be? How else could we help the whole of what we're doing? Lot's of simple compare contrasts that would be done faster, and be more accurate, and inclusive, if they were done by somebody or something else if it mattered and I wanted it done to a measureable standard. [Horizontal Search for inclusion] A computer is fully capable of searching a lot more stuff than I am, a lot faster. And I could just decide from that right/wrong, good, better, best, yes/no, around 5, probably okay, but you it would be advisable to monitor the situation. ]
    1. We use GUIDs in two directions in our security algorithms, and in our overall application management processes from multiple perspectives. EATS is all about perspectives and view points integration.
      1. We use it to identify who members are, with all "unknowns" falling into a general category. See: Membership
      2. We use it to tag content
      3. We use it to identify ownership relationships over content and proprietary materials (so not everything is an "open book")
      4. We use it to identify and manage "maps" of relationships and activities and processes between members (humans, people, users) and stuff (information, processes, activities, roles, responsibilities, defenders of rationales and ideas, originators of conceptsCredit needs to be properly attributed to original authors, especially if they are elders and may have lived generations ago. Attribution need not be to current living people. Wikipedia has a nice catalog started. They is no problem assigning a GUID to every page on Wikipedia, and mapping to that. It's something we will eventually want to do anyway.)
  3. Every member gets an ID assigned by EATS, 

"Keys" to facilities are currently formed from a trust hierarchy based on these fundamentals. This is our confidentiality exposure point, or at least the most consequential ones, I think. Any member who is aware of a weakness in this scheme should report it to system management at their earliest convenience. 

 

Is there an open specification or something on this. It should be checked to see whether this "complies" or how it would rank. Is it superior, other than the fact that it integrates coverage into everything everywhere in the model. My assumption was basically what I've already got documented (in an incompatible form right now) based on "RBAC(?) + GUIDs + Scrambling and multiplexing" was a pretty good security facility. 

 

We want to do 98+ or maybe 99.9998, I don;t know which, as "open" material and process. Most "proprietary" should be in"back-end" knowledge content systems. Our concerns:

  1. We want to be a "trusted" party to secure "personal" data, as required, to instill and ensure trust by members when they need to keep selected information "private." Member's have a "right" to privacy of personal information and IP.
  2. We want to be a "trusted" conduit/courier  for content that may be communicated through an EATS architected space. Wax seals are insufficient for that task these days.
  • 1. If I had better software I wouldn't have to write like this, and you wouldn't have to read it like this, whoever you are. I hope you are making your way through this. At whatever level you are reading it. It's one document, aimed at a lot of levels, from a lot of different perspectives, all at the same time. The editor I have constructed on my latest prototype EATS model would be a much better way for me to write this documentation. And that's what all this stuff is folks, documentation. Anyway, the editor works better, and clears up massive (well, not massive but problems) with getting it to be both write-friendly and read-friendly and appropriated "componentized" and "cataloged"  while I write it. This is bad on both sides.[Architectural Analysis] I'm taking the time, from time to time to try to include notes. Notes that a simple, reasonably simple, computer algorithm could follow. ..

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
SystemsThinking