#hacksandheels

[hacksandheels]

5 of 11

This past week I had my mid-internship interview with my supervisor. Which is crazy, because it means I’ve been living in California for five weeks but also means my summer is half over.

[hacksandheels]

I’ve been on hiatus for a while now, for a lot of reasons all of which boil down to mental health being more important than anything else. But I’m home and getting better by the day, and will hopefully be posting new content soon :)

[hacksandheels]

Extra Credit Blog Entry - Databases

As technology and data science has evolved, methods of storing the ever growing collection of data points has expanded right along with it. Relational databases such as SQL, MYSQL and Oracle were eventually joined data systems such as noSQL and MongoDB, designed to agile handle large influxes of data. Each type of databases has its own advantages and disadvantages that make it uniquely suited to different types of data handling situations. Neither is inherently better or worse despite what software war zealots may try to convince you.

The relational database was developed in 1970 by E.F. Codd at IBM. This type of database is composed of collections of data items organized into formally structured tables from which the data can be extracted or reassembled without having to reorganize the database tables. Structured Query Language, or SQL, as it is more commonly called, is used for interacting with and modifying the database. Relative databases are fairly easy to setup and access, and have the advantage of being easy to expand upon. A new category can be added to the database without needing a total overhaul of the application, only a few tweaks.

The relational database is built as a set of tables (each of which is sometimes referred to as a “relation”). The tables contain data that fits into predefined categories established at the initial setup of the table. Each table will contain at least one data category as a column, but there are usually more. Each row contains a unique entry of data with the attributes of the columns.  For example, a database of student information might include the student’s name, student ID number and year. Another table might describe that student’s GPA for each class they are enrolled in. A user of this database can obtain a custom view that presents only the information of interest to them; for example a user could sort by student’s with above a certain GPA to determine who should be on the honor roll that semester.  Or the teacher of a specific class could view all students in that class with below a certain GPA to determine who may need extra help. The table entries are rigid however, a string cannot be inserted where the table is expecting an integer, etc.  In short, a relational database creates sets of data using matching characteristics, and those sets are termed as schema.

NoSQL options have existed since before SQL, dating back to 1960, but have only recently gained popularity through implementations such as MongoDB and Apache Cassandra. In handling the that large volume of data that is now commonplace, being organized and well structured can actually create a problem.  NoSQL databases are much less structured, which at large volumes can increase speed. No longer does the very rigid approach of SQL work in taking in and managing large sets of varying data types. In NoSQL unstructured data can be stored across multiple processing nodes and doesn’t requires a fixed table. The advantage of not needing a fixed table is you don't need to know in advance what kind of data will be collected and stored. The format of the data being stored can be changed at any time without the application throwing a hissy fit. More data of varying types can be collected and analyzed at a quicker speed than with relational databases.

Those multiple processing nodes can even be spread across multiple servers in a distributed architecture that allows high levels of horizontal scalability. As the data set increases the hardware can be scaled up without performance repercussions. NoSQL databases are usually designed with lower cost hardware in mind, making expanding less expensive. However, NoSQL is not entirely comprised of advantages to more static SQL systems. NoSQL is not nearly as widely implemented and therefore needs some time to prove itself before acceptance by mainstream businesses. It still has a long way to go in terms of maturing. Customer support is often better in SQL databases and they are much friendly to code, whereas NoSQL requires much deeper levels of programming to run a query.

Both types of databases are the best at what they do. When used properly each can provide advantages.  SQL is better suited to logically related data sets that can be pre-identified and in which data integrity is of importance. NoSQL can more efficiently handle unrelated and evolving data sets then need intense speed and scalability. As always, think about the situation at hand and go with the solution that suits your enterprise best, not whatever happens to be the fad at the moment.

http://www.sitepoint.com/sql-vs-nosql-differences/

https://blog.udemy.com/nosql-vs-sql-2/

http://searchsqlserver.techtarget.com/definition/relational-database

[hacksandheels]

Managed Service Provider (MSP) - An Overview

It seems that almost every aspect of our lives, from social to economic require some sort of technical expertise. Filing taxes online, ordering a last minute birthday present from Amazon, even now cars require some technical institution to navigate the increasing number of features. As individuals we can grow and adapt, but business face a much larger challenge. In order to keep up  in almost industry there must be technical infrastructure.  The cost of that infrastructure alone is a large expense, maintaining it even more.  Many small to medium businesses don’t have the same in house expertise that larger companies can afford to hire. The small IT department often ends up overwhelmed.  Managed service providers have stepped in to fill that gap.

A MSP is a company that will remotely manage a customer company’s technical infrastructure. They originated with large Fortune 500 countries that could afford networks in the early days of computing. Simple Network Management Protocol was developed in the early 90s and was applied to PCs. As with most early software, the management systems for monitoring PCs and turning that data into useful output were complex, geared towards large scale and prohibitively expensive.  As systems became more mature they could apply their benefits to smaller systems.  

 The MSP will monitor systems on a proactive basis, and usually for a flat monthly fee.  The fee will be negotiated based on services provided and a the number of devices to be monitored.  Basic services often start with just a monitoring system that alerts the customer of issues to be resolved by the client. At the upper end of the price spectrum the provider can offer fully managed service that cover the process from monitoring through problem resolution. Different packages can be priced at different levels, allowing the service to expand as the client business expands. This model is different that usual IT projects, such as the instillation of a server or phone system, which holds a one time investment for the customer company and a one time revenue gain for the MSP. The services to be provided are outlined in a service level agreement that is signed at the beginning of the relationship. This contractual arrangement denotes the performance and quality metrics that will be used to asses the performance of the MSP.  

This monthly subscription model will often end up being cheaper for small companies. At many small to medium businesses the only time something will get fixed is once it is broken. This might appear to be the most efficient model, but the business will suffer losses while the IT department scrambles to fix the issues. An MSP will often employ remote 24 hour monitoring and management software on the client’s infrastructure in order to remotely troubleshoot and solve issues with the customer's setup. Through proactive monitoring of potential issues the client company can avoid downtime and loss of revenue. They can provide supervision of backups, patches and manage security.  The MSP provides the expertise and support that a large IT department might provide but at a fraction of the price.

However, these are not the end all be all, and should be considered carefully. Depending on the type of business looking to outsource its IT, there may be regulations to consider. Not to mention that your network has been exposed to an outsider, regardless of how trustworthy that outsider might be. There may be security risks to consider and potentially sensitive data that is now exposed. It is also important to investigate whether or not the provider can modify its approach to suite your business and its needs to specifically.

A managed service provider can be very beneficial to small and medium sized businesses without the resources to manage their own IT infrastructure. These services can eliminate problems before they occur and be an efficient use of a small budget.  As always, as a network administrator it is best to investigate all options and choose the one that best suites your own network and infrastructure.

http://www.imagineiti.com/it-support/understanding-managed-services/

http://searchenterprisewan.techtarget.com/definition/managed-service-provider

[hacksandheels]

4.17.16

40/100 - Today was The First Good Day, which is totally not a thing I just made up. You know that day when everything is sunny and its clear winter is really truly over? That was today. It was beautiful. I worked super hard in the lab for two hours right after brunch to finish my Network Forensics Assignment, which was an adventure and a half. Then I headed down to the waterfront to read, went out for dinner with my roommate, and had a quiet evening updating my planner and getting ready for the week. 

[hacksandheels]

Tag 20 followers you’d like to know better

I was tagged by @thisgirlcodes

Name: Emily

Star sign: Leo (ya’ll should check out @musterni-illustrates and the Shitty Horoscope collection on the blog, its AMAZING)

Average hours of sleep: I function (well) on anywhere from five hours and up, but tend to aim for eight. 

Lucky number: Big fan of 3 for whatever reason. 

Last thing I googled: 2:30PST in EST

Favorite fictional characters: Hmm. Right now, Ender from Ender’s Game. But my forever love is Hermione Granger because she is everything I want to be in life. 

When did I start this blog: January or February of this year. 

Amount of followers: 67

What do I post mostly: Studyblr, how to life, women in STEM,

Do I run any more blogs: Yup

Why did I get this url: I don’t fit the usual stereotype of the information security industry. I don’t want to change who I am to try and fit in; I like being me. So I’m trying to incorporate my very arguable feminine tastes and personality in to a career I love very much. Thus, hacksandheels. Has a nice ring to it too. 

Tagging @colour-code @ai-effect @2nvtech @curiosityandcode @curlyscience and @writingmywayout

[hacksandheels]

4.10.16

33/100 - Spent the majority of my afternoon in two different labs cranking out assignments, yes I brought my slippers to the lab and was very happy with that choice. In the cybersecurity lab I finally wrangled my server core in to submission using windows powershell. I'd never really used powershell before, but it was pretty straightforward with the help of some technical guides. In the digital forensic lab I finished off a Trump themed Encase assignment; those beady eyes stared me down the entire time. Side note: I have a deep seated love of hex editors for whatever reason. Such a nifty way to look at data.

[hacksandheels]

Thanks to @thisgirlcodes for tagging me!

Tag you're it! You've been tagged as a fantastic woman in tech to talk about your experience as a woman in this field. Many women report feeling shut out or afraid to pursue careers in STEM subjects, especially computer science, so what's your experience with this if you have any? Also check out zwicking cause she made a similar survey and I would really appreciate it if you could answer her as well :D once you've finished tag 3 other people to answer this as well!

My first inspiration to get in to STEM was was a teacher in middle school. She encouraged my (mostly female) squad to compete in the local rendition of the Future City Competition. We came in basically dead last for two years but my interest in building things and re-imaging the way the world worked was fueled by that team and the endless encouragement our teacher had. Going in to STEM wasn't a question; it was my destiny. So I never really thought about the thinning ranks of females in my classes or the gender gap that grew each passing year. I was an good student and to be honest, a bit of a teacher's pet. I loved my tech classes. I think thats why getting in to the field I never felt afraid; I had the best grades in the class, damn right I deserved to be there. I was blessed with some amazing mentors and classmates along the way as well. My best friend of over a dozen years was right beside me the entire way, and is now studying electrical engineering. This backstory is important, because the fact that when I first announced my intent to be an engineer I was met with nothing less than full support has helped make me who I am today. For years I never once questioned that I could succeed at whatever the hell I wanted.

It honestly wasn't till I got to college that I started seriously considering the role my gender played in my career. If I had doubts in high school, it was in the idea that I just simply wasn't smart enough to achieve my dreams. College is a little different. I'm a lot more aware now. I still wouldn't say that I have been outright discouraged in the way many others have. I consider myself very lucky to have a supportive family, faculty and generally accepting student body. Its the little things now, but I have strong enough roots that I barely notice it. I am the girl. It isn't good, it isn't bad, it just is. I expect that as I progress in to the field I may very well run in to more trouble, but for now I'm a lucky individual.

I tag @pointer-to-void, @colour-code and anyone else who wants to jump in!