from Naked Security http://ift.tt/2s5gfyv
via https://ifttt.com/ IFTTT
This post Egnyte Launch New Data Security Innovation in the Cloud appeared first on CloudTweaks Connected CloudTweaks.
New Data Security Innovation Cisco predicted in their 2016 White Paper, entitled Cisco Global Cloud Index: Forecast and Methodology 2015–2020, that by the end of 2020 annual global cloud IP traffic will reach 14.1 ZB (1.2 ZB per month), up…
This post Egnyte Launch New Data Security Innovation in the Cloud appeared first on CloudTweaks Connected CloudTweaks.
There’s bad news for internet music fans, as it has been revealed that the details of millions of users of the 8tracks internet radio service and music social network have been stolen by hackers.
The post 8tracks Hacked: 18 Million User Account Details Stolen appeared first on The State of Security.
This post Research Report: Emergency Management Leaders Discuss the Security of Mobile, Remote Workers appeared first on CloudTweaks Connected CloudTweaks.
The Security of Mobile, Remote Workers Everbridge, Inc., a global software company that provides critical event management and enterprise safety applications to help keep people safe and businesses running, recently announced the findings of its research into the safety of mobile, remote…
This post Research Report: Emergency Management Leaders Discuss the Security of Mobile, Remote Workers appeared first on CloudTweaks Connected CloudTweaks.
An investigation conducted by City of London Police and Microsoft culminated in the arrests of four UK persons accused of perpetrating tech support scams. On 27 June 2017, officers from North East Regional Special Operations Unit (NERSOU) placed a 37-year-old man and 35-year-old woman living in South Shields under arrest. Authorities later released those two individuals […]… Read More
The post Four UK Persons Arrested for Perpetrating Microsoft Tech Support Scams appeared first on The State of Security.
The iPhone was released on June 29, 2007. It wasn't the first smartphone - smartphones have been in existence since the 1990's - but it's clearly the smartphone that truly launched the mobile revolution.
Recode's How Apple’s iPhone changed the world: 10 years in 10 charts covers some of the amazing changes that the iPhone has brought with it.
It has charts and data on things like the growth of data traffic, phones replacing cameras, its impact on advertising, etc.
But our favorite is it's impact on chewing gum sales.
As the article chart below shows, gum sales have declined substantially since the release of the iPhone.
The reason, according to the article, is we're now too busy looking at our phones in check-out lines to buy gum. Key article quote:
Supermarket checkout lines — strategically stocked with magazines and candy — were for a long time a major point of sale for gum. Consumers waiting on line to pay would look around and make impulse buys. Now, however, we’re so consumed with our phones that we’re not reaching for a pack of gum to stave off our boredom.
This is a great example of secondary effects and unintended consequences (we assume Steve Jobs was not targeting gum sales with the iPhone).
As the article points out there must be many more examples:
"Have drug dealing and other illegal activities become more efficient thanks to the smartphone’s discreet payment model? Has English become more prominent as English-language-based mobile apps connect the developing world? Have smartphones and the omnipresent connectedness they provide enabled the rise of helicopter parents, niche communities or better literacy."
One example we've spotted is walkers distracted by cellphones are leading to increasing rates of pedestrian accidents, injuries and fatalities. This is resulting in cities deploying new types of in ground traffic lights so folks looking down at their cellphones can see them.
The picture below is of a new traffic light in the Dutch town of Bodegraven.
There are no doubt many more examples.
There is quite a bit of NIST security noise that should not be dismissed. Whether you are a federal agency or not, NIST has significant meaning for you. The National Institute of Standards Technology (NIST) is a lab and federal non-regulated agency organization that offers guidance to promote innovation and industrial competitiveness. When it comes […]… Read More
The post What’s All This NIST Security Noise About? appeared first on The State of Security.
Another not cloudy but brilliant morning to wake up to. It might be summer somewhere. But I don’t need a clock radio. Instead, I consume news from around the world at breakfast or on the way to some office. But “I Got You Babe” seems to be playing everywhere. Clearly, I am not actually in […]… Read More
The post Groundhog Day 2017 – or Any Other Day appeared first on The State of Security.
New course releases are first available for Early Access through the Citrix Learning Center. The Citrix Learning Center, located …
Similar to Fintech revolutionizing the financial services industry, Insurtech is taking the insurance sector by storm with its innovative and possibly disruptive technology solutions. The benefits to incumbent insurers include better engagement with and reestablishing trust with customers, the ability to innovate quicker with improved products, services and distribution, increased operational efficiency and profits, the ability to generate meaningful risk insight, and the opening of new market opportunities for millennials seeking easier means of purchasing insurance.
However, the transition to an Insurtech business model comes with its challenges as many insurance companies are mired in old legacy systems with high cultural barriers that could serve as roadblocks to adoption. As well, Insurtech startups are replete with their own challenges as they try and break into a highly regulated, long established market with an entrenched customer base.
An upcoming issue of Cutter Business Technology Journal with Guest Editor Steve Andriole invites papers that address how Insurtech is bringing both innovation and disruption to the insurance industry.
Discussion points may include the following:
1. How can traditional insurance companies benefit from integrating Insurtech technologies into current business models?
2. What are the challenges of integrating Insurtech innovations?
3. What are some of the emerging Insurtech business models and technologies?
4. What new vendors are entering the Insurtech market?
5. What mutual benefits can be achieved by the collaboration between startups and incumbents?
6. What threats do startups pose to traditional insurance carriers?
7. How can Insurtech improve the customer experience?
8. What is the impact of Insurtech on governance, compliance and risk?
9. How can Insurtech technologies be integrated into an incumbent’s ecosystem?
10. What impact will Insurtech startup companies have in the insurance industry?
11. What advantages do incumbent insurers have over startups and vice versa?
12. What are some of the main challenges faced today by Insurtech startups?
13. How are AI, machine learning and robotics being used to improve decision making and processes?
To submit an article idea, please email Christine Generali at cgenerali[at]cutter[dot]com and Steve Andriole at steve[dot]andriole[at]gmail[dot]com.
ARTICLE DEADLINE: AUGUST 18, 2017
In object-oriented programming, an “interface” is a description of the things an object can do. Usually, this takes the form of a list of methods an object is guaranteed to have. C# and Java both support interfaces, and so does the Go programming language, but Go’s interfaces are especially easy to use.
You don’t have to declare that a Go type (which is kind of like a “class” in other languages) implements an interface, like you do in C# or Java. You just declare the interface, and then any type that happens to have those methods can be used anywhere that interface is required.
Let’s suppose that I have a pets package (a “package” is like a “library” in other languages) with Dog and Cat classes. A Dog has a Fetch method, a Cat has a Purr method, and most importantly, both dogs and cats have Walk and Sit methods.
package pets
import "fmt"
type Dog struct {
Name string
Breed string
}
func (d Dog) Walk() {
fmt.Println(d.Name, "walks across the room")
}
func (d Dog) Sit() {
fmt.Println(d.Name, "sits down")
}
func (d Dog) Fetch() {
fmt.Println(d.Name, "fetches a toy")
}
type Cat struct {
Name string
Breed string
}
func (c Cat) Walk() {
fmt.Println(c.Name, "walks across the room")
}
func (c Cat) Sit() {
fmt.Println(c.Name, "sits down")
}
func (c Cat) Purr() {
fmt.Println(c.Name, "purrs")
}
Now, let’s create a demo.go program that shows what the Dog and Cat types can do. We’ll create a DemoDog function that takes a Dog and calls its Walk and Sit methods. Then we’ll create a DemoCat function that does the same thing, but for cats.
package main
import "pets"
func DemoDog(dog pets.Dog) {
dog.Walk()
dog.Sit()
}
func DemoCat(cat pets.Cat) {
cat.Walk()
cat.Sit()
}
func main() {
dog := pets.Dog{"Fido", "Terrier"}
cat := pets.Cat{"Fluffy", "Siamese"}
DemoDog(dog)
// The above call outputs:
// Fido walks across the room
// Fido sits down
DemoCat(cat)
// The above call outputs:
// Fluffy walks across the room
// Fluffy sits down
}
It’s too bad, though: the DemoDog and DemoCat functions are exactly the same, except that one takes a Dog and the other takes a Cat. Repeating code like that increases the risk of bugs. It would be nice if we could get rid of DemoCat and just pass a Cat to DemoDog, but we’ll get an error if we try that:
DemoDog(cat)
// ./demo.go:19: cannot use cat (type pets.Cat)
// as type pets.Dog in argument to DemoDog
But we don’t have to maintain two nearly-identical functions, just because they take different types. This is exactly the problem that interfaces are meant to solve.
We’ll just create a FourLegged interface that includes all types with Walk and Sit methods. Then we’ll replace the DemoDog and DemoCat functions with a single Demo function that takes any FourLegged value (whether it’s a Dog or a Cat).
package main
import "pets"
// This interface represents any type
// that has both Walk and Sit methods.
type FourLegged interface {
Walk()
Sit()
}
// We can replace DemoDog and DemoCat
// with this single function.
func Demo(animal FourLegged) {
animal.Walk()
animal.Sit()
}
func main() {
dog := pets.Dog{"Fido", "Terrier"}
cat := pets.Cat{"Fluffy", "Siamese"}
Demo(dog)
// The above call (again) outputs:
// Fido walks across the room
// Fido sits down
Demo(cat)
// The above call (again) outputs:
// Fluffy walks across the room
// Fluffy sits down
}
We didn’t have to update the Dog or Cat types to declare that they implement the FourLegged interface (like we would in C# or Java). We didn’t even have to open the pets package. We just declared our interface right there in our main program, right above the function where we use it. And because they both have Walk and Sit methods, the Dog and Cat types are automatically usable any place in our code that calls for a FourLegged value!
Go interfaces are a low-ceremony way to keep the safety of static typing (like you see in C# or Java), while still offering most of the flexibility of dynamic typing (like in JavaScript or Python). And they’re just one of the language’s many programmer-friendly features. If you’re suitably impressed, you should look into Go further; you won’t be disappointed!
P.S.: I’ve made the code from this post available in a Treehouse Workspaces snapshot. You can try running the code right from your browser by forking it and typing go run demo.go in the workspace console.
P.P.S: This post was adapted from Go Language Overview. It’s our new course for developers already proficient in programming, who want a quick primer on Go. We’ll be releasing courses for beginning Go programmers too, so keep an eye on our library!
Start learning to code today with a free trial on Treehouse.
The post Go Interfaces are Awesome appeared first on Treehouse Blog.
What is GDPR?
The General Data Protection Regulation (GDPR) was approved and adopted by the EU Parliament in April 2016, and replaces the …
On June 27, 2017, a digital attack campaign struck banks, airports and power companies in Ukraine, Russia and parts of Europe. Security experts who analyzed the attack determined its behavior was consistent with a form of ransomware called Petya. They also observed the campaign was using a familiar exploit to spread to vulnerable machines. Let’s […]… Read More
The post NotPetya: Timeline of a Ransomworm appeared first on The State of Security.