ykankaya Goto Github PK

followers: 219.0 following: 1.7K repos: 10.6K gists: 15.0

Name: y.kankaya

Type: User

Company: Entropy Creative

Bio: I'm a primitive living form from earth planet

Location: Earth Planet

y.kankaya's Projects

As a insurance company we've been asked to develop an application that manage some information about our insurance policies and company clients. To do that, we have two services that provide us with all the data needed: * The list of company clients can be found at: http://www.mocky.io/v2/5808862710000087232b75ac * The list of company policies can be found at: http://www.mocky.io/v2/580891a4100000e8242b75c5 With that information, we need to create a Web API that exposes services with some constraints: * Get user data filtered by user id -> Can be accessed by users with role "users" and "admin" * Get user data filterd by user name -> Can be accessed by users with role "users" and "admin" * Get the list of policies linked to a user name -> Can be accessed by users with role "admin" * Get the user linked to a policy number -> Can be accessed by users with role "admin" We have the following constraints: * REST Web API should be developed using MVC WebAPI * Think about licenses of 3d party libraries (if needed) * Authentication and authorization. Take the user role from the web service that returns the list of company clients As our stakeholders are very fussy, here you have some tips: * Usage of last technologies * Solution properly structured * Usage of patterns * Add everything you thing it's needed to ensure product's quality.

backendeasyweb

admin url

backstab

A tool to kill antimalware protected processes

backstopjs

Catch CSS curve balls.

backstroke

:swimmer: A Github bot to keep repository forks up to date with their upstream

bad-pdf

Steal Net-NTLM Hash using Bad-PDF

badassmacros

BadAssMacros - C# based automated Malicous Macro Generator.

badblood

BadBlood by @davidprowe, Secframe.com, fills a Microsoft Active Directory Domain with a structure and thousands of objects. The output of the tool is a domain similar to a domain in the real world. After BadBlood is ran on a domain, security analysts and engineers can practice using tools to gain an understanding and prescribe to securing Active Directory. Each time this tool runs, it produces different results. The domain, users, groups, computers and permissions are different. Every. Single. Time.