Editing 2044: Sandboxing Cycle
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
− | A {{w|Sandpit|sandbox}} or sandpit is a playground where children can play safe without interfering | + | {{incomplete|Created by a CONTAINER BOT (otherwise new comic pages and much more would have to be created here manually) - Please change this comment when editing this page. Do NOT delete this tag too soon.}} |
+ | |||
+ | A {{w|Sandpit|sandbox}} or sandpit is a playground where children can play safe without interfering the world outside. By this meaning the term was adopted by others like the {{w|Sand table|sand table}} in military uses, or as a {{w|Wikipedia:Sandbox|Wikipedia Sandbox}}, a playground for inexperienced editors to test their additions, and in computer security which [[Randall]] probably references at this comic. | ||
Software is getting more and more complex, and in an effort to reduce programming work and security vulnerabilities, large applications are composed of multiple programs. Getting these mostly self-contained programs to work with each other can be tricky, since requirements can vary a lot between different applications, requiring a rather general {{w|Interface (computing)|interface}} or {{w|API}} for communication. The more open such interfaces are, the higher the risk of unintended side effects, like vulnerabilities and overly permissive data access which could be exploited by hackers. | Software is getting more and more complex, and in an effort to reduce programming work and security vulnerabilities, large applications are composed of multiple programs. Getting these mostly self-contained programs to work with each other can be tricky, since requirements can vary a lot between different applications, requiring a rather general {{w|Interface (computing)|interface}} or {{w|API}} for communication. The more open such interfaces are, the higher the risk of unintended side effects, like vulnerabilities and overly permissive data access which could be exploited by hackers. | ||
− | |||
− | + | At first, we are presented with an application whose parts are not yet fully connected to each other, suggesting the application has not yet been fully developed. Some of them are encapsulated and don't talk directly with programs on the outside, but through the encapsulation layer. | |
− | + | Using some "new technology" these parts are interconnected, with blatant disregard to good software design (foregoing encapsulation (as they are being drawn from an inner circle 'cutting' through its container), too much data sharing, even a connection that seemingly leads nowhere). | |
− | + | Randall then notices that the programs making up his service have a very high number of connections between them, reducing the sandboxing effort to absurdity (and probably gaining a few security holes along the way). | |
− | + | One solution to this problem is {{w|Sandbox (computer security)|sandboxing}}. Sandboxing a program limits its access to the outside world transparently. This can tighten up sloppy security by working around it. A direct consequence of restricted communication is that it is now harder to connect programs with each other. The Industry currently puts a lot of work into {{w|Orchestration (computing)|orchestrating}} these sandboxes; making it (supposedly) easier to plug programs into each other without sacrificing security. | |
+ | |||
+ | He then proceeds to re-sandbox his services without cleaning up the mess he made and the cycle starts over. | ||
The dilemma is again stated in the title text: Randall wants both ease of use and high security. In practice, a tradeoff has to be made. | The dilemma is again stated in the title text: Randall wants both ease of use and high security. In practice, a tradeoff has to be made. | ||
− | |||
− | |||
==Transcript== | ==Transcript== | ||
Line 42: | Line 43: | ||
:[The arrow above the fourth panel connects it to the first and the circle continues from the beginning.] | :[The arrow above the fourth panel connects it to the first and the circle continues from the beginning.] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{comic discussion}} | {{comic discussion}} | ||
Line 54: | Line 48: | ||
[[Category:Comics with color]] | [[Category:Comics with color]] | ||
[[Category:Charts]] | [[Category:Charts]] | ||
− |